ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel


Updated on April 22, 2012

Following section provides an in depth description of IPv6 configuration in BIND. All the details and examples are given assuming the reader has the basic knowledge on DNS, BIND and BIND configuration etc. In order to have the IPv6 capability in our DNS server we need to do several configuration changes. With the installation of BIND, all the DNS data will be located in /var/named folder. It contains the zone files and other related data.

Following basic changes and enhancements should be done in the /etc/named.conf boot file in order to operate over IPv6.

  • Configure the server to listen for incoming queries sent using IPv6.

listen-on-v6 { any; };

Server will listen on default port 53 for any IPv6 address.

listen-on-v6 port 2000 { 2001:df0:17:c00:1::2222; };

Server will listen on port 2000 for only the specified address.

If no listen-on-v6 option is specified, the server will not listen on any IPv6 address unless -6 is specified when named is invoked. If -6 option is specified, then named will listen on port 53 on all IPv6 interfaces by default.

  • Set the other options as same for IPv4 by only replacing the IPv4 addresses with preferred IPv6 addresses.

allow-query { 2001:df0:17:c00::/64;;};

allow-transfer { 2001:df0:17:c00::/64; };

allow-recursion { 2001:df0:17:c00::/64; };

  • zone transfers

!The zone transfer is initiated by the slave server. Example configuration is shown below for a slave server in order to fetch zone files for the zone “” form the master server 2001:df0:17:e00::1.

zone "" {

type slave;

masters { 2001:df0:17:e00::1; };

file "";

transfer-source-v6 { 2001:df0:17:e00::4444; }; };

Following configuration option needs to be set in the slave server in order to fetch zones transferred inbound by the server. In the master server (here 2001:df0:17:e00::1), address of the slave server should be specified within the allow-transfer statement.


  • Current ACL statements should be modified to include ipv6 addresses.

Forward resolution

For the locally administered domains, we need to add following type of zone details in the named.conf file. General configuration procedure for IPv4 is not affected by IPv6 for this process.

zone "” {

type master;

file "";


For each locally administrated zone, zones file need to be created in the /var/named/ directory as follows.

$TTL 86400

@ IN SOA (

20100212 ; Serial

604800 ; Refresh

86400 ; Retry 2419200 ; Expire

604800 ) ; Negative Cache TTL

;; DNS server

@ IN NS ;;dual stack nodes www IN A IN AAAA 2001:df0:17:e00::4:2222 Cache IN A IN AAAA 2001:df0:17:e00::4:3333 Lms IN A IN AAAA 2001:df0:17:e00::4:4444 ;;ipv6 only test lab www6 IN AAAA 2001:df0:17:e00::1111 lms6 IN AAAA 2001:df0:17:e00::2222 pc1 IN AAAA 2001:df0:17:e00::3331 pc2 IN AAAA 2001:df0:17:e00::3332 pc3 IN AAAA 2001:df0:17:e00::3334

Reverse resolution

Configuring the BIND nameserver for reverse resolution is much troublesome task due to the longer IPv6 addresses. For each domain the network address should reversed digit-wise.

Configuration for the 2001:df0:17:e10::/64

;;for 2001:df0:17:e10::/64

zone "" {

type master;

file "2001:df0:17:e10.db";


Corresponding reverse zone file will be as follows,

$TTL 86400 @ IN SOA ( 20100212 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL @ IN NS $ORIGIN 200 IN PTR 201 IN PTR 202 IN PTR

;; test ipv6 lab $ORIGIN IN PTR


pure ipv6 name resolution

For a pure IPv6 name resolution process, all the nodes from the root name servers to the final authoritative name server should be IPv6 supported. But in the current scenario this is not yet achieved for most of the cases.

IPv6 support in the root name servers is not fully implemented. Only 7 of the 13 root servers are ipv6 capable.

In the internet there are three types of DNS servers.

1. IPv4 only (only reachable by IPv4)

2. IPv6 only (only reachable by IPv6)

3. Dual stack (reachable by both IPv4 and IPv6)

According to the DNS IPv6 Transport Operational Guidelines presented in RFC3901, it suggests all the recursive name servers to be either IPv4 only or dual-stack. It also suggests that each DNS zone need to have at least one IPv4-reachable DNS server (which is the current situation). For the dual stack name resolution to be consistent this must be adhered. We cannot have IPv6 reachable server for each domain.

The reason for this suggestion is to avoid the fragmentation of the name space. Consider a pure IPv6 name resolution process by a recursive DNS server. It may get halted if it encounters a DNS server which can be reached only in IPv4. Same thing would happen for the pure IPv4 name resolution in the transition period.

So in most of the cases pure IPv6 name resolution is halted without completing the required resolution. So in the initial phase of the transition we need to adhere to the above best practice.


    0 of 8192 characters used
    Post Comment

    No comments yet.


    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at:

    Show Details
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the or domains, for performance and efficiency reasons. (Privacy Policy)
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)