nameserver registration and IPv6

[kriteknetworks]

Hi folks, I run three nameservers, all are registered with my registrars and work fine. Part of said registration is providing the registrar with the ipv4 IP and fqdn of the nameservers. I have these servers also listening on ipv6 addresses that I've mapped to the fqdn used by these servers.
My question is: am I required to notify the registrar of the addition of the ipv6 addresses?
And do the root nameservers, some now ipv6, need to know my servers ipv6 addresses?
Or is it simply sufficient to have AAAA records for the fqdn of the servers?
Thanks

[snarked]

As discussed elsewhere, many registrars and some registries cannot handle IPv6 glue records yet.  Therefore, it is currently "simply sufficient" to have AAAA records retrievable when addresses of your servers are queried for.

[kriteknetworks]

As discussed elsewhere, many registrars and some registries cannot handle IPv6 glue records yet.  Therefore, it is currently "simply sufficient" to have AAAA records retrievable when addresses of your servers are queried for.

If there is no glue, queries will always come, and be responded to, in ipv4, correct?
Thus having AAAA records in the zone for my NSs won't do anything since the root NSs don't have the glue.
Do I understand this correctly?

[testmonster]

In order to be able to run fully native, there should be glue AAAA host records for your nameservers in the appropriate TLD zone,
and the TLD nameservers involved should have AAAA records and support native IPv6 queries.

Several of the root servers already have AAAA records and respond to native IPv6 queries.

The next two components are the TLDs and registrars.

Some TLDs have AAAA records (such as .com and .net) and respond to native IPv6 queries.

Some example registrars that support IPv6 for domain names they host:

http://www.enom.com/
http://gkg.net/
http://www.bookmyname.com/

If you use a registrar because they support IPv6 and you have a good experience then please let everybody here know.
Let us know if it was completely supported via their normal web interface (preferred) or if you had to call or email to specially request it.

[kriteknetworks]

Heh almost word for word from the sixxs dns faq...I sent email to my registrar requesting ipv6 glue info.
I was also told today that joker.com registrar now supports ipv6 glue via their web interface.

[snarked]

Thus having AAAA records in the zone for my NSs won't do anything since the root NSs don't have the glue.  Do I understand this correctly?

No.  The first query will be IPv4, but once the AAAA record gets cached, it may be used.

Regardless, the root DNS servers won't have your NS records either.  Maybe you meant the TLD servers.

[eonesixfour]

No.  The first query will be IPv4, but once the AAAA record gets cached, it may be used.

Only if there is no AAAA glue records ;)

Regardless, the root DNS servers won't have your NS records either.  Maybe you meant the TLD servers.

Isn't that kinda the same thing in the case of .com and .net domains?
I didn't see, or I over looked what domain the OP was talking about so it depends on that as to who would store any glue records.

[kriteknetworks]

Its a .com, and I'm awaiting completion of a domain transfer to a registrar that supports ipv6 ns addressing.

[kriteknetworks]

Domain transfer complete. NSs updated with IPv6 glue records. Happy camper indeed.

Here's a question: Does the org tld not have ipv6 glue? I notice ultradns has a few servers using ipv6.

[snarked]

.org doesn't support IPv6 glue - at the registry.

[karlbrose]

Code Select Expand

; <<>> DiG 9.4.2 <<>> @a.root-servers.net org.
; (2 servers found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30831
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 11
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;org.                           IN      A

;; AUTHORITY SECTION:
org.                    172800  IN      NS      C0.ORG.AFILIAS-NST.INFO.
org.                    172800  IN      NS      D0.ORG.AFILIAS-NST.org.
org.                    172800  IN      NS      TLD1.ULTRADNS.NET.
org.                    172800  IN      NS      TLD2.ULTRADNS.NET.
org.                    172800  IN      NS      A0.ORG.AFILIAS-NST.INFO.
org.                    172800  IN      NS      B0.ORG.AFILIAS-NST.org.

;; ADDITIONAL SECTION:
A0.ORG.AFILIAS-NST.INFO. 172800 IN      A       199.19.56.1
A0.ORG.AFILIAS-NST.INFO. 172800 IN      AAAA    2001:500:e::1
B0.ORG.AFILIAS-NST.org. 172800  IN      A       199.19.54.1
B0.ORG.AFILIAS-NST.org. 172800  IN      AAAA    2001:500:c::1
C0.ORG.AFILIAS-NST.INFO. 172800 IN      A       199.19.53.1
C0.ORG.AFILIAS-NST.INFO. 172800 IN      AAAA    2001:500:b::1
D0.ORG.AFILIAS-NST.org. 172800  IN      A       199.19.57.1
D0.ORG.AFILIAS-NST.org. 172800  IN      AAAA    2001:500:f::1
TLD1.ULTRADNS.NET.      172800  IN      A       204.74.112.1
TLD1.ULTRADNS.NET.      172800  IN      AAAA    2001:502:d399::1
TLD2.ULTRADNS.NET.      172800  IN      A       204.74.113.1

;; Query time: 92 msec
;; SERVER: 2001:503:ba3e::2:30#53(2001:503:ba3e::2:30)
;; WHEN: Wed May 21 00:53:36 2008
;; MSG SIZE  rcvd: 411


[snarked]

Non-sequitur.

.org may be served from IPv6 enabled servers, but that still doesn't mean that it supports IPv6 glue records for domains registered through its registry.  PIR doesn't support IPv6 glue.

[eonesixfour]

PIR doesn't support IPv6 glue.

Which I find comical in an ironic twist since on their website they list 2 people, almost in a boastful way, involved with national IPv6 deployment in 2 different countries. When I emailed them I got back the most boring form reply, I half felt like tracking down email addresses and emailing the 2 people listed on their website to find out what they think about PIR's stance on IPv6.

[snarked]

PIR has announced on July 31, 2008, that it is testing IPv6 glue for the .org TLD.  Available "shortly" for all.

http://blog.pir.org/ - 3rd entry of 3 on that date.

[snarked]

.ORG now supporting IPv6 glue.