I have a Centos server that is running BIND and has IPv6 global addresses.
I have entered a number of AAAA records into this copy of BIND in a local view and zone (tld is htt).
Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back.
But if I try to use the IPv6 address of the system I get a time out. Both from nslookup and from ping6.
I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server).
I have turned off both ip6tables and iptables so it is not a firewall issue.
Even 'nslookup - <ipv6 addr>' does not work. I seem to recall a problem with nslookup supporting udp over IPv6, but ping6 should not have that problem.
This is all on the single system running BIND. I figure i got to get that working before worrying about other systems!
Robert Moskowitz wrote on Mon, 29 Dec 2008 17:21:48 -0500:
nslookup
is deprecated. Did you try with host? May give you the same result, but, well ..
I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server).
You used ::1 then?
Kai
Kai Schaetzl wrote:
Robert Moskowitz wrote on Mon, 29 Dec 2008 17:21:48 -0500:
nslookup
is deprecated. Did you try with host? May give you the same result, but, well ..
So what tool has replaced it? I have only been using nslookup for some 14 years...
I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server).
You used ::1 then?
nslookup - ::1
also had 'connection timeout, no servers could be reached'.
Which would be expected if nslookup does not support IPv6 (particularly if it has been deprecated and replaced with something else, what).
I changed /etc/resolv.conf to have:
nameserver ::1
in it, and ping6 -n host.htt. still got 'unknown host'
Robert Moskowitz wrote:
Kai Schaetzl wrote:
Robert Moskowitz wrote on Mon, 29 Dec 2008 17:21:48 -0500:
nslookup
is deprecated. Did you try with host? May give you the same result, but, well ..
So what tool has replaced it? I have only been using nslookup for some 14 years...
'host'
John R Pierce wrote:
Robert Moskowitz wrote:
Kai Schaetzl wrote:
Robert Moskowitz wrote on Mon, 29 Dec 2008 17:21:48 -0500:
nslookup
is deprecated. Did you try with host? May give you the same result, but, well ..
So what tool has replaced it? I have only been using nslookup for some 14 years...
'host'
Argh. I like nslookup in command mode better.....
So 'host host.htt. -6' (and without the -6 and with ::1) does not work.
My /var/named/chroot/etc/named.conf does have the 'query-source-v6 53;' line in it and 'netstat -na|grep 53|more' shows a
udp 0 0 :::53 :::*
line, indicating that NAMED is listening on IPv6, and destination or source address.
So what am I missing?
Kai Schaetzl a écrit :
Robert Moskowitz wrote on Mon, 29 Dec 2008 17:21:48 -0500:
nslookup
is deprecated.
it's no more deprecated (should we say: it is "re-precated"? :). I don't have a pointer right now (but run it and you should no more get a warning...).
Did you try with host? May give you the same result, but, well ..
I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server).
You used ::1 then?
Kai
Mouss wrote on Tue, 30 Dec 2008 14:52:08 +0100:
(but run it and you should no more get a warning...).
Yeah, almost first thing I noticed when moving from Suse to CentOS. I attributed this rather to some error, though.
Kai
Robert Moskowitz wrote:
I have a Centos server that is running BIND and has IPv6 global addresses.
I have entered a number of AAAA records into this copy of BIND in a local view and zone (tld is htt).
Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back.
But if I try to use the IPv6 address of the system I get a time out. Both from nslookup and from ping6.
I setup /etc/resolv.conf as shown at: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SYSADV5/p13.html (the only hit I got on configuring resolv.conf for an IPv6 DNS server).
I have turned off both ip6tables and iptables so it is not a firewall issue.
Even 'nslookup - <ipv6 addr>' does not work. I seem to recall a problem with nslookup supporting udp over IPv6, but ping6 should not have that problem.
This is all on the single system running BIND. I figure i got to get that working before worrying about other systems!
Per http://tldp.org/HOWTO/Linux+IPv6-HOWTO/hints-daemons-bind.html
I found out that I had to add to the options section in named.conf:
listen-on-v6 { any; };
It is obvious that the line:
query-source-v6 port 53;
Was not what is needed.
Grumble, grumble.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
John R Pierce -
Kai Schaetzl -
mouss -
Robert Moskowitz