About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: [ipv6-wg@localhost] Re: RIPE NCC's DNS server available in IPv6

  • From: Aleksi Suhonen < >
  • Date: Mon, 09 Dec 2002 07:38:20 +0200

Hello,

Quote from Carlos Friacas:
} But this raises me one more question: Does someone know if there are *any*
} AAAA (glue-)records on that/(similar) zone(s) yet?

I understand that "jp." has had IPv6 name servers for a while now.
These are slightly abbreviated for ease of reading:

% dig jp. ANY @ns0.nic.ad.jp
...
;; ANSWER SECTION:
jp.                     86400   IN      NS      ns0.nic.ad.jp.
jp.                     86400   IN      SOA     ns0.nic.ad.jp. bind-admin.nic.ad
.jp. 2002120901 3600 900 604800 86400
jp.                     86400   IN      NS      ns.wide.ad.jp.
jp.                     86400   IN      NS      ns0.iij.ad.jp.
jp.                     86400   IN      NS      dns0.spin.ad.jp.
jp.                     86400   IN      NS      ns-jp.sinet.ad.jp.
jp.                     86400   IN      NS      ns-jp.nic.ad.jp.

...
;; ADDITIONAL SECTION:
ns0.nic.ad.jp.          86400   IN      A       202.12.30.131
ns.wide.ad.jp.          86400   IN      AAAA    2001:200:0:1::4
ns.wide.ad.jp.          86400   IN      A       203.178.136.63
ns0.iij.ad.jp.          86400   IN      AAAA    2001:240::53
ns0.iij.ad.jp.          86400   IN      A       202.232.2.34
dns0.spin.ad.jp.        86400   IN      A       165.76.0.98
ns-jp.sinet.ad.jp.      86400   IN      A       150.100.2.3
ns-jp.nic.ad.jp.        86400   IN      A       61.120.151.100
...
% dig nl. ANY @ns.domain-registry.nl.
...
;; ANSWER SECTION:
nl.                     345600  IN      NS      ns.domain-registry.nl.
nl.                     345600  IN      NS      ns.ripe.net.
nl.                     345600  IN      NS      auth02.ns.uu.net.
nl.                     345600  IN      NS      ns2.domain-registry.nl.
nl.                     345600  IN      NS      sunic.sunet.se.
nl.                     345600  IN      NS      ns2.nic.fr.
nl.                     345600  IN      SOA     ns.domain-registry.nl. hostmaster.domain-registry.nl. 200212060 28800 14400 2592000 345600

...
;; ADDITIONAL SECTION:
ns.domain-registry.nl.  345600  IN      A       193.176.144.2
ns2.domain-registry.nl. 345600  IN      A       193.176.144.130

...
% dig nl. ANY @sunic.sunet.se.
...
;; ADDITIONAL SECTION:
ns.domain-registry.nl.  345600  IN      A       193.176.144.2
ns.ripe.net.            172800  IN      AAAA    2001:610:240:0:193::193
ns.ripe.net.            172800  IN      A       193.0.0.193
auth02.ns.uu.net.       516     IN      A       198.6.1.82
ns2.domain-registry.nl. 345600  IN      A       193.176.144.130
sunic.sunet.se.         86400   IN      A       192.36.125.2
ns2.nic.fr.             31778   IN      A       192.93.0.4
...
% 


CONCLUSION: Now that the ns.ripe.net contains an AAAA record, it
too is starting to seep into the TLDs that ns.ripe.net is a secondary
name server for. As was said, asking the root servers about "nl."
still doesn't give any AAAA glue records.

But why don't ns*.domain-registry.nl and auth02.ns.uu.net provide
full glue records for the name servers?

--
	Aleksi Suhonen / Axu TM Oy



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community