On Thu, 16 Jun 2011 02:45:53 -0500 DJ Lucas <[email protected]> wrote: > Hmm, latest version of Bind is working fine for me 9.8.0-P2, though I > had to rejig the test suite patch because they added ipv6 interface tests. > > root@anu [ /sources/smbldap-tools-0.9.6 ]# nslookup > > > Server: 192.168.143.225 > Address: 192.168.143.225#53 > > Non-authoritative answer: > www.nhs.uk canonical name = www.prod.nhs.uk.akadns.net. > Name: www.prod.nhs.uk.akadns.net > Address: 217.64.234.65 > > > > Double check the format and perms of your root.hints file. That address > is A.ROOT-SERVERS.NET and is rather odd that it is looking at the AAAA > host for an A record (especially if no IPv6 GW is setup). > > Latest hints file is dated June 8th, 2011, and added only the AAAA > record for D, and changed the TTL for L's AAAA record from 7D to 41.6_D > (like the rest). Book is current for all A records, but AAAA records > should probably be added at some point (because I like that format much > better than the one at IANA/internic). Probably also need to add ::1 to > /etc/hosts in LFS at some point soon enough.
I had updated to the latest root.hints file. I've since edited it to get rid of the AAAA records but to no avail, I still get this error: Jun 16 12:29:21 eccles named[26648]: createfetch: nhs.uk A Jun 16 12:29:21 eccles named[26648]: createfetch: . NS Jun 16 12:29:21 eccles named[26648]: error (network unreachable) resolving 'nhs.uk/A/IN': 2a01:40:1001:35::2#53 Jun 16 12:29:23 eccles named[26648]: createfetch: nsa.nhs.uk AAAA Jun 16 12:29:23 eccles named[26648]: createfetch: nsb.nhs.uk AAAA Jun 16 12:29:51 eccles named[26648]: client 127.0.0.1#54742: query failed (SERVFAIL) for nhs.uk/IN/A at query.c:6199 I've updated to bind-9.8.0-P2 (and worked around a bug using ssl in chroot) but it still doesn't work. It's very annoying. Bruce Dubbs <[email protected]> wrote: > I agree with you that it appears to be an IPV6 issue, but the > question is how would it get fixed? There would need to be some sort of > active proxy to get from an IPV4 address to an IPV6 address. > > Perhaps named just inquires via the kernel. Is IPV6 enabled there? IPv6 was enabled in the kernel, but as I don't have an IPv6 connection I'd only enabled IPv6 in IPv4 tunneling. I've since recompiled the kernel and enabled a lot more IPv6 options but it hasn't made any difference. Thanks for your time Andy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
