Hi, FYI, the IEDR in it's capacity as ccTLD manager of .ie have added a new IPv6 compatible name server ns6.iedr.ie. Additionally, we have added AAAA glue for one of our slaves ns3.ns.esat.net. ns3.ns.esat.net also slaves for the folks at .tp Kind regards -- ________________________________ Billy Glynn Network Operations Centre IE Domain Registry Ltd Tel: +353 (0)1 2365404 Mobile: +353 (0)87 9188317 billy.glynn@domainregistry.ie ________________________________
On Mon, 2004-09-06 at 19:05, Billy Glynn wrote:
Hi,
FYI, the IEDR in it's capacity as ccTLD manager of .ie have added a new IPv6 compatible name server ns6.iedr.ie. Additionally, we have added AAAA glue for one of our slaves ns3.ns.esat.net. ns3.ns.esat.net also slaves for the folks at .tp
Neat, 2 IPv6 nameservers in the root for .ie. 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. RIPE NCC folks ? :) Greets, Jeroen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFBPVn5P0gnkXA27R8RAtu1AJ9doEPoSpXoJdKksX748X9/6bdwcwCfWKcY +ZLAVn6HthZDoqu0WN3qJa8= =TfJ6 -----END PGP SIGNATURE-----
On 07.09 08:49, Andreas S. Kerber wrote:
uuh, I guess that would get pretty close to 512 bytes when querying ie.
So what? See below for examples of what could happen: soem glue is omitted. If the client supports IPv6 it almost certainly supports EDNS(0), so the 512 byte limit is no issue. If the lient does not support EDNS some glue may be dropped for very long names without problems. See http://www.nlnetlabs.nl/ipv6/publications/v6rootglue.pdf for a little more detail. (It can be argued that dropping AAAA glue first is a good tactic here because "see above". This will be implemented on all root name servers in the near future.) Daniel ----- ; <<>> DiG 8.2 <<>> @k.root-servers.net. short.ie. ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 12 ;; QUERY SECTION: ;; short.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ice.netsource.ie. 2D IN A 212.17.32.2 ns6.iedr.ie. 2D IN A 213.190.149.221 ns6.iedr.ie. 2D IN AAAA 2001:bb0:ccc3::2 ;; Total query time: 71 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:29:37 2004 ;; MSG SIZE sent: 26 rcvd: 499 ; <<>> DiG 8.2 <<>> @k.root-servers.net. something.verylogindeed.fordemopurposes.ie ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 11 ;; QUERY SECTION: ;; something.verylogindeed.fordemopurposes.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ice.netsource.ie. 2D IN A 212.17.32.2 ns6.iedr.ie. 2D IN A 213.190.149.221 ;; Total query time: 69 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:29:43 2004 ;; MSG SIZE sent: 60 rcvd: 505 ; <<>> DiG 8.2 <<>> @k.root-servers.net. something.verylogindeed.fordemopurposes.evenlonger.toforceommittingmoreglue.ie ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 10, ADDITIONAL: 9 ;; QUERY SECTION: ;; something.verylogindeed.fordemopurposes.evenlonger.toforceommittingmoreglue.ie, type = A, class = IN ;; AUTHORITY SECTION: ie. 2D IN NS ns2.nic.fr. ie. 2D IN NS ns.ripe.net. ie. 2D IN NS banba.domainregistry.ie. ie. 2D IN NS uucp-gw-1.pa.dec.com. ie. 2D IN NS uucp-gw-2.pa.dec.com. ie. 2D IN NS ns3.ns.esat.net. ie. 2D IN NS gns1.domainregistry.ie. ie. 2D IN NS gns2.domainregistry.ie. ie. 2D IN NS ice.netsource.ie. ie. 2D IN NS ns6.iedr.ie. ;; ADDITIONAL SECTION: ns2.nic.fr. 2D IN A 192.93.0.4 ns.ripe.net. 2D IN A 193.0.0.193 banba.domainregistry.ie. 2D IN A 193.1.142.2 uucp-gw-1.pa.dec.com. 2D IN A 204.123.2.18 uucp-gw-2.pa.dec.com. 2D IN A 204.123.2.19 ns3.ns.esat.net. 2D IN A 192.111.39.100 ns3.ns.esat.net. 2D IN AAAA 2001:7c8:2:a::64 gns1.domainregistry.ie. 2D IN A 198.133.199.102 gns2.domainregistry.ie. 2D IN A 198.133.199.103 ;; Total query time: 67 msec ;; FROM: dienst.karrenberg.net to SERVER: k.root-servers.net. 193.0.14.129 ;; WHEN: Tue Sep 7 11:33:53 2004 ;; MSG SIZE sent: 96 rcvd: 509
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
On 08.09 09:57, Andrei Robachevsky wrote:
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."
That is correct. It depends what a reasonable query is. If I was IANA I would advise .ie strongly to rationalise the names in their glue to save space. However, my point is that exceeding this limit will not cause the sky to fall down. Daniel
Hi, On 07 Sep, Jeroen Massar wrote: | On Mon, 2004-09-06 at 19:05, Billy Glynn wrote: | > Hi, | > | > FYI, the IEDR in it's capacity as ccTLD manager of .ie have added a new | > IPv6 compatible name server ns6.iedr.ie. | > Additionally, we have added AAAA glue for one of our slaves | > ns3.ns.esat.net. ns3.ns.esat.net also slaves for the folks at .tp | | Neat, 2 IPv6 nameservers in the root for .ie. | | I also see that you have ns2.nic.fr listed in there, ns3.nic.fr has IPv6 | for sure. ==> ns2.nic.fr has been supporting IPv6 for several months. We published it's IPv6 address a couple of weeks ago and we intend to ask for sticking its AAAA in . soon. By the way, we will use 'b.nic.fr' instead of 'ns2.nic.fr' as we used 'c.nic.fr' instead of 'ns3.nic.fr' for fr AAAA glue under . Mohsen. | | 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. | | RIPE NCC folks ? :) | | Greets, | Jeroen
participants (6)
-
Andreas S. Kerber -
Andrei Robachevsky -
Billy Glynn -
Daniel Karrenberg -
Jeroen Massar -
Mohsen Souissi