Hi,
I´m in the process of testing BIND 9.7.0.1 (from ports) on FreeBSD 8.0 with IPv6.
The system has both IPv4 and IPv6 IP address, both are working. I found after adding some AAAA records I was getting errors looking them up, but I could look them up from a Windows 7 laptop :S
On further digging I have tested with a public IPv6 forward DNS record:
altavista.ipv6.digital.com
My FreeBSD fails if I attempt to do a lookup on this via nslookup, equally fails a ping. However a valid AAAA records exists which I can see from Windows 7 and also via a dig from FreeBSD.
I have replaced base BIND with BIND 9.7 and chosen to force IPv6 support. I can see by the datestamp on my nslookup binary its just been compiled. So whats the problem? I had a look on the freebsd site at the IPv6 guide and dont see any reference to having to make special changes to be able to see IPv6 DNS records....
thanks, Andy.
I´m in the process of testing BIND 9.7.0.1 (from ports) on FreeBSD 8.0 with IPv6.
The system has both IPv4 and IPv6 IP address, both are working. I found after adding some AAAA records I was getting errors looking them up, but I could look them up from a Windows 7 laptop :S
On further digging I have tested with a public IPv6 forward DNS record:
altavista.ipv6.digital.com
My FreeBSD fails if I attempt to do a lookup on this via nslookup, equally fails a ping. However a valid AAAA records exists which I can see from Windows 7 and also via a dig from FreeBSD.
I have replaced base BIND with BIND 9.7 and chosen to force IPv6 support. I can see by the datestamp on my nslookup binary its just been compiled. So whats the problem? I had a look on the freebsd site at the IPv6 guide and dont see any reference to having to make special changes to be able to see IPv6 DNS records....
thanks, Andy.