Global IPv6 Report

[patrickdk]

Is there something wrong with the global ipv6 report? I notice it updates everyday, and sometimes every other day.

But it seems atleast .us domains with aaaa glue still say 0, even though my domain has had it for a month now.

us   1613896   1238132     26796     13921         0  (Sat Jun 26 01:03:28 2010)  (Sat Jun 26 06:39:57 2010)

[mleber]

Is there something wrong with the global ipv6 report? I notice it updates everyday, and sometimes every other day.

But it seems atleast .us domains with aaaa glue still say 0, even though my domain has had it for a month now.

us   1613896   1238132     26796     13921         0  (Sat Jun 26 01:03:28 2010)  (Sat Jun 26 06:39:57 2010)

What is your domain that is in the .us TLD?

BTW, this whole subject is a bit perplexing and requires more investigation.

For example, take the domain SCHMALENBERGER.US.

$ dig AAAA SCHMALENBERGER.US @i.cctld.us

; <<>> DiG 9.4.2-P2.1 <<>> AAAA SCHMALENBERGER.US @i.cctld.us
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43425
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;SCHMALENBERGER.US.      IN   AAAA

;; AUTHORITY SECTION:
SCHMALENBERGER.US.   7200   IN   NS   NS3.SCHMALENBERGER.US.
SCHMALENBERGER.US.   7200   IN   NS   NS.PRGMR.COM.
SCHMALENBERGER.US.   7200   IN   NS   NS2.AFRAID.ORG.
SCHMALENBERGER.US.   7200   IN   NS   NS2.SCHMALENBERGER.US.

;; ADDITIONAL SECTION:
NS2.SCHMALENBERGER.US.   7200   IN   A   69.104.45.180
NS2.SCHMALENBERGER.US.   7200   IN   AAAA   2002:4568:2db4::1
NS3.SCHMALENBERGER.US.   7200   IN   A   216.218.223.115
NS3.SCHMALENBERGER.US.   7200   IN   AAAA   2001:470:1:41::d8da:df73

;; Query time: 66 msec
;; SERVER: 2001:503:d1ae:ffff:ffff:ffff:ffff:ff7e#53(2001:503:d1ae:ffff:ffff:ffff:ffff:ff7e)
;; WHEN: Sat Jun 26 21:40:30 2010
;; MSG SIZE  rcvd: 213

However if we check the .us TLD (access contract agreement) we don't find those AAAA records.  Here is how it looks:

# show that we have the current version

$ zcat us.zone.gz | head
$TTL 900
us. IN SOA a.gtld.biz. hostmaster.gtld.biz. (
   32520407 ; Serial
   900 ; Refresh
   900 ; Retry
   604800 ; Expire
   86400 ) ; Minimum
;
; Generation start time = JUN-25-2010 19:51:34
; TLD RECORDS

# now look for a NS2.SCHMALENBERGER.US glue record that would be found in the .us TLD zone file:

$ zcat us.zone.gz | grep -i  NS2.SCHMALENBERGER
NS2.SCHMALENBERGER IN A 69.104.45.180
SCHMALENBERGER IN NS NS2.SCHMALENBERGER.US.

So where the heck is it?!!

I've looked before, looked just now, and will poke around more.

Mike.

[patrickdk]

The is patdk.us

[snarked]

Using http://network-tools.com/nslook/

Questions
name class type
patdk.us IN NS

Answer records
name class type data time to live
patdk.us IN NS ns2.patdk.us 3600s (1h)
patdk.us IN NS ns1.patdk.us 3600s (1h)
patdk.us IN NS ns4.patdk.us 3600s (1h)
patdk.us IN NS ns3.patdk.us 3600s (1h)
Authority records
(none)
Additional records
name class type data time to live
ns3.patdk.us IN A 74.95.90.234 3600s (1h)
ns1.patdk.us IN A 66.36.239.126 3600s (1h)
ns2.patdk.us IN A 66.36.239.125 3600s (1h)
ns4.patdk.us IN A 66.36.239.111 3600s (1h)
-- end --

No IPv6 addresses let alone glue in your zone.

I do see the AAAA records at a.cctld.us (serving the parent zone, ".US"), but your zone data lacks the records.  Since your address records for your name servers do not match the glue records at the parent zone, your zone fails.

See http://www.nabber.org/projects/dnscheck/?domain=patdk.us&ipv6=on for details.  It reports:  No AAAA glue for ns1.patdk.us.

[patrickdk]

Please learn how to do dns tools or something, that website so isn't working for ipv6.

I have double checked all the glue and zone records and they all match perfectly and return A and AAAA records.

And if the admin notes there is a problem.

[patrickdk]

Ok, I didn't notice the link at the bottom of your post. But if you bother to read what that site says, it says only that ns1.patdk.us doesn't have glue, ALL others do.

I left ns1.patdk.us without glue, for the same purpose he.net leaves out one of their servers from being ipv6 compatabile, in the case someone has an ipv6 network setup that isn't connected to the rest of the internet, It would fail on all nameservers that have ipv6 ip's.

[snarked]

Right, but the fact that I was getting inconsistent results still means that something is wrong.