---
title: "Is it possible to configure BIND to use both IPv6 and IPv4 ?"
slug: "aa-00821"
description: "By default, BIND (prior to version 9.10) did not listen for client queries on IPv6, but it could be enabled. In newer versions of BIND, it is the default."
tags: ["listen on", "IPv6"]
updated: 2018-10-12T20:53:20Z
published: 2018-10-12T20:53:20Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.isc.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Is it possible to configure BIND to use both IPv6 and IPv4 on the same server?

By default, BIND (prior to version 9.10) does not listen for client queries on IPv6, but you can enable it by adding this option:

```
listen-on-v6 { any; };
```

This will cause **named** to listen on all IPv4 and IPv6 configured interfaces.

listen-on-v6 default changed in BIND 9.10The default `none;` setting for **listen-on-v6** was changed in BIND version 9.10. Now `listen-on-v6 { any; };` is the default. It can be overridden with the `named -4` command line option.

By default, BIND will use both IPv4 and IPv6 transport (if available) when performing recursionWhen **named** is performing recursion, it will learn the names and addresses (both A and AAAA RRsets) for nameservers authoritative for domains that might be able to provide the answers to client queries. If IPv6 transport is available, then **named** will try both the IPv6 and IPv4 addresses that it has learned when contacting those authoritative servers, and for determining which are the fastest servers to respond. This behavior can be overridden with the `named -4` command line option, which will cause **named** to only use IPv4 when performing recursion.