DNS servers with IPv6

[brahama]

Hi guys,

I'm really new in this IPv6 thing... I really dont understand how to config my DNS for IPv6 and how it depends on TLD supporting glue records... dunno what glue records is.. been searching but havent found anything clear...

I would like to start with that clarification... what are glue records and which dns has to support them..

Thanks a lot

[kristiankrohn]

* http://www.sixxs.net/faq/dns/?faq=ipv6glue (Page content seems unavailable at this time)
* http://209.85.129.132/search?q=cache:vJbD-QumaQIJ:www.sixxs.net/faq/dns/%3Ffaq%3Dipv6glue+glue+records+sixxs&cd=1&hl=en&ct=clnk&gl=de&client=firefox-a (Google cache of the page mentioned above)

* http://en.wikipedia.org/wiki/Domain_Name_System#Circular_dependencies_and_glue_records

Sorry for the short answer. I'm not impolite -- just drunk ;)

[brianegge]

I've changed my name server to xname.org, as they appear to offer free ipv6 dns.  The changes seem to have propagated ok, and I can see a AAAA record for the ns2 name server.  Are my dns settings correct?  Will the test pass even though only one of the name servers is IPv6 enabled?

dig ns eggeadventure.com

; <<>> DiG 9.4.2-P2 <<>> ns eggeadventure.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9557
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 4

;; QUESTION SECTION:
;eggeadventure.com.      IN   NS

;; ANSWER SECTION:
eggeadventure.com.   172800   IN   NS   ns0.xname.org.
eggeadventure.com.   172800   IN   NS   ns1.xname.org.
eggeadventure.com.   172800   IN   NS   ns2.xname.org.

;; ADDITIONAL SECTION:
ns1.xname.org.      122   IN   A   87.98.164.164
ns2.xname.org.      122   IN   A   88.191.64.64
ns2.xname.org.      122   IN   AAAA   2a01:e0b:1:64:240:63ff:fee8:6155
ns0.xname.org.      122   IN   A   195.234.42.1

[broquea]

If you mean the Sage cert test, yes 1 is all you need. If it isn't working right away it might be a caching issue. If it isn't working after a few days, I might need to reload the caching NS.