Hello! I am trying to perform the Guru DNS tests, and it seems to be failing, even though my authoritative DNS servers are IPv6 enabled and have AAAA records for them.
When I perform the test, it immediately bounces back with Couldn't get AAAA for NS. It would be very helpful if it produced a little more output so that maybe I could figure out what is going on. Everything seems OK here, and I can see everything using dig from several networks.
I am trying to test neillt.com... here is some dig output from my end, querying my upstream Time Warner Business Class DNS servers...
$ dig neillt.com any
; <<>> DiG 9.4.2-P2 <<>> neillt.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6407
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; QUESTION SECTION:
;neillt.com. IN ANY
;; ANSWER SECTION:
neillt.com. 30039 IN NS xen-server.neillt.com.
;; AUTHORITY SECTION:
neillt.com. 30039 IN NS xen-server.neillt.com.
;; ADDITIONAL SECTION:
xen-server.neillt.com. 30039 IN A 67.52.144.205
xen-server.neillt.com. 30039 IN AAAA 2001:470:1f05:216:21c:c0ff:fe77:64b4
;; Query time: 21 msec
;; SERVER: 66.75.160.15#53(66.75.160.15)
;; WHEN: Sun Nov 23 08:56:47 2008
;; MSG SIZE rcvd: 111
I also looked at what is coming across from my AT&T Cell Data card...
Neill:~ neillt$ dig neillt.com any
; <<>> DiG 9.4.2-P2 <<>> neillt.com any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34408
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;neillt.com. IN ANY
;; ANSWER SECTION:
neillt.com. 172731 IN NS dns2.thorconsulting.org.
neillt.com. 172731 IN NS xen-server.neillt.com.
;; AUTHORITY SECTION:
neillt.com. 172731 IN NS xen-server.neillt.com.
neillt.com. 172731 IN NS dns2.thorconsulting.org.
;; ADDITIONAL SECTION:
xen-server.neillt.com. 172731 IN A 67.52.144.205
xen-server.neillt.com. 172731 IN AAAA 2001:470:1f05:216:21c:c0ff:fe77:64b4
;; Query time: 142 msec
;; SERVER: 209.183.54.151#53(209.183.54.151)
;; WHEN: Sun Nov 23 09:05:04 2008
;; MSG SIZE rcvd: 162
And just in case it's the secondary DNS server record screwing it up there... here is the dig for that server.
; <<>> DiG 9.4.2-P2 <<>> dns2.thorconsulting.org any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26843
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1
;; QUESTION SECTION:
;dns2.thorconsulting.org. IN ANY
;; ANSWER SECTION:
dns2.thorconsulting.org. 3600 IN A 67.52.144.204
dns2.thorconsulting.org. 3600 IN AAAA 2001:470:1f05:216:21c:c0ff:fe77:64b4
;; AUTHORITY SECTION:
thorconsulting.org. 3600 IN NS ns17.domaincontrol.com.
thorconsulting.org. 3600 IN NS ns18.domaincontrol.com.
;; ADDITIONAL SECTION:
ns17.domaincontrol.com. 8877 IN A 216.69.185.9
;; Query time: 2189 msec
;; SERVER: 209.183.54.151#53(209.183.54.151)
;; WHEN: Sun Nov 23 09:05:54 2008
;; MSG SIZE rcvd: 156
If anyone has any clue on what might be screwing this up, I am all ears. To be honest, I don't know what it is.