|
|
 |
Re: [dns-wg] IPv6 in .ie
- Date: Wed, 08 Sep 2004 09:57:52 +0200
Andreas S. Kerber wrote:
On Tue, Sep 07, 2004 at 08:39:08AM +0200, Jeroen Massar wrote:
I also see that you have ns2.nic.fr listed in there, ns3.nic.fr has IPv6
for sure.
You should maybe ask RIPE NCC if they can stick glue for ns.ripe.net
into the . also with an IPv6 address, which would also give quite a
number of other TLD's etc an IPv6 capable nameserver all of a sudden.
uuh, I guess that would get pretty close to 512 bytes when querying ie.
# dig -t NS ie. @a.root-servers.net | grep MSG
;; MSG SIZE rcvd: 493
I think adding another AAAA record will actually exceed this limit.
Daniel wrote:
So what? See below for examples of what could happen:
soem glue is omitted.
But also the IANA procedure will not permit it:
"5. If the number of name servers or IP addresses in the delegation
exceeds eight (8), the size of responses to reasonable queries with the
intended delegation will be checked to ensure that such responses fit
into a 512 byte UDP packet. This is the standard size limitation for UDP
response packets for most resolving name server software on the Internet
today."
Coming back to the issue with ns.ripe.net. The fact that it is a
secondary for about 90 ccTLDs makes it impossible to insert AAAA record
in the root for any of the zone, because that will affect others.
Currently, we are planning to introduce a scheme whereby each ccTLD has
its own name in the ripe.net domain, eg:
ns-ie.ripe.net A 193.0.12.107
AAAA 2001:610:240:0:53:cc:12:107
All of the addresses for ccTLDs (ns-XX.ripe.net) are simply IP aliases
on a shared machine.
Regards,
Andrei Robachevsky
RIPE NCC
|
|
|
|
