Bind 9.2.0 and IPv6

[Dwyane Everts_1]

All,

There are numberous postings about Bind 9.2, and others about IPv6. What I need is info for configuring Bind 9.2 to handle IPv6. We don't use IPv6 yet, and don't have plans to in the near furture, so how can I configure Bind to ignore IPv6 altogether? I have Bind 9.2.0 installed on a D-class HP-UX 11i server.

Thanks in advance!!
D

[Steven E. Protter · Accepted solution]

IPv6 is only available for HP-UX 11i, btw.

Though it may be part of the installation, a standard installation of bind 9.2.x will ignore IPv6 unless you tell it otherwise.

A standard installation includes a /etc/named.conf file which points to zone files in /var/named

Implementing IPv6 involves changes to the network structure of the machine, in /etc/rc.config.d/netconf . If you don't implment it there BIND will ignore it.

Background:
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/5187-2255/5187-2255_top.html&con=/hpux/onlinedocs/5187-2255/00/01/112-con.html&toc=/hpux/onlinedocs/5187-2255/00/01/112-toc.html&searchterms=Ipv6%7cBIND&queryid=20031024-052811
http://docs.hp.com/hpux/onlinedocs/B5969-4338/B5969-4338.pdf

There is a good BIND doc on this linux site and thats what I used to set up both HP-UX and Linux servers
http://tldp.org/HOWTO/DNS-HOWTO.html

SEP

[James Specht]

You don't have to do anything to ignore IPv6. You have to add the follow to have BIND listen for IPv6 traffic. I don't have anything special and I don't have IPv6 either and BIND works fine.

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

Two great BIND books are
"DNS & BIND Cookbook" ISBN 0-596-00410-9
"DNS & BIND" ISBN 0-596-00158-4

--Jim

[Dwyane Everts_1]

Gents,

I appreciate your entries in such a timely manner (WOW!!). I have the book "DNS & BIND Cookbook." So, let me explain my issue more thoroughly, since IPv6 shouldn't be installed. This error is shutting my DNS off, and the ITRC search I did told me to configure the "OPTION listen-on-v6 { any; } ;" <-- even though I'm not using IPv6!!

Here is the error, any clues why I'm seeing this?

Oct 23 14:53:57 named[3753]: shutting down
Oct 23 14:53:57 named[3753]: no longer listening on #53
Oct 23 14:53:57 named[3753]: no longer listening on 127.0.0.1#53
Oct 23 14:53:59 named[28494]: starting BIND 9.2.0
Oct 23 14:53:59 named[28494]: using 2 CPUs
Oct 23 14:53:59 named[28494]: loading configuration from '/etc/named.conf'
Oct 23 14:53:59 named[28494]: no IPv6 interfaces found
Oct 23 14:53:59 named[28494]: listening on IPv4 interface lan0, 172.24.10.20
#53
Oct 23 14:53:59 named[28494]: could not listen on UDP socket: address in use
Oct 23 14:53:59 named[28494]: creating IPv4 interface lan0 failed; interface ignored
Oct 23 14:53:59 named[28494]: listening on IPv4 interface lo0, 127.0.0.1#53
Oct 23 14:53:59 named[28494]: zone 'domain.com' allows updates by IP addres
s, which is insecure
Oct 23 14:53:59 named[28494]: none:0: open: /etc/rndc.key: file not found
Oct 23 14:53:59 named[28494]: couldn't add command channel 127.0.0.1#953: file not found
Oct 23 14:53:59 named[28494]: no source of entropy found

[James Specht]

First off it looks like something is running against the UDP port.

Oct 23 14:53:59 named[28494]: could not listen on UDP socket: address in use

Find out what that is. Either a named service is still running or some other app has that port.

Second your rndc.key is either missing or was not created.

Oct 23 14:53:59 named[28494]: none:0: open: /etc/rndc.key: file not found

Since you have the cookbook I'll just point you there and not repeat it here. Go to 3.2 page 50 and read about the rndc feature.

Once that is working everything else should fall into place.

Last, go ahead and ignore the IPv6 line. It's just telling you that there is no IPv6 interface to worry about. It's simply information and not a error.

Oct 23 14:53:59 named[28494]: no IPv6 interfaces found

--Jim

[Dwyane Everts_1]

Gents,

Your inputs are well worth the points!!! Thank you much!!!! Now I have some reading to do....

D