IPv6 Nameserver Question with dig +trace

[Noel Butler]

On Mon, 2012-01-23 at 22:02 -0500, Kevin A. McGrail wrote:

> Hi All,
> 
> On an older Bind server such as 9.3.6-p1, I can run dig +trace www.pccc.com.
> 
> However, when I'm using 9.8.1-p1 and seeing a problem that stops the 
> trace when it reaches our IPv6 nameserver, ns3.pccc.com.  Examples follow.
> 
> Am I doing something wrong with the newer dig?
> 
> Regards,
> KAM
> 
> dig +trace www.pccc.com @ns.pccc.com
> 
> ; <<>> DiG 9.8.1-P1 <<>> +trace www.pccc.com @ns.pccc.com
> ;; global options: +cmd
> .                       175250  IN      NS      g.root-servers.net.
> .                       175250  IN      NS      h.root-servers.net.
> .                       175250  IN      NS      i.root-servers.net.
> .                       175250  IN      NS      j.root-servers.net.
> .                       175250  IN      NS      k.root-servers.net.
> .                       175250  IN      NS      l.root-servers.net.
> .                       175250  IN      NS      m.root-servers.net.
> .                       175250  IN      NS      a.root-servers.net.
> .                       175250  IN      NS      b.root-servers.net.
> .                       175250  IN      NS      c.root-servers.net.
> .                       175250  IN      NS      d.root-servers.net.
> .                       175250  IN      NS      e.root-servers.net.
> .                       175250  IN      NS      f.root-servers.net.
> ;; Received 512 bytes from 38.100.17.53#53(38.100.17.53) in 155 ms
> 
> com.                    172800  IN      NS      j.gtld-servers.net.
> com.                    172800  IN      NS      d.gtld-servers.net.
> com.                    172800  IN      NS      m.gtld-servers.net.
> com.                    172800  IN      NS      k.gtld-servers.net.
> com.                    172800  IN      NS      l.gtld-servers.net.
> com.                    172800  IN      NS      e.gtld-servers.net.
> com.                    172800  IN      NS      b.gtld-servers.net.
> com.                    172800  IN      NS      g.gtld-servers.net.
> com.                    172800  IN      NS      a.gtld-servers.net.
> com.                    172800  IN      NS      f.gtld-servers.net.
> com.                    172800  IN      NS      i.gtld-servers.net.
> com.                    172800  IN      NS      c.gtld-servers.net.
> com.                    172800  IN      NS      h.gtld-servers.net.
> ;; Received 502 bytes from 192.36.148.17#53(192.36.148.17) in 201 ms
> 
> pccc.com.               172800  IN      NS      ns.2rad.net.
> pccc.com.               172800  IN      NS      ns.pccc.com.
> pccc.com.               172800  IN      NS      ns2.pccc.com.
> pccc.com.               172800  IN      NS      ns3.pccc.com.
> dig: couldn't get address for 'ns3.pccc.com': not found
> 


Likely because ns3 has only ipv6 address and no ipv4 address and the
server you are checking from has no ipv6 capability.
You are asking for big problems using this method.
You should give all NS records an IPv4 address, and then add in IPv6 on
the ones you can

eg:

ns2                     A       ip.v.4.add
ns2                     AAAA    ip:6:addr

I guess the old versions are not so strict on checking, or dont know
what to do about ipv6



-- 
Noel Butler <noel.butler at ausics.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20120124/a100d166/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20120124/a100d166/attachment.bin>