[ipv6-wg@ripe.net] Re: [dns-wg] IPv6 in .ie
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
On 7-sep-04, at 11:40, Daniel Karrenberg wrote:
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.)
So then nothing stands in the way of adding AAAA glue records to the root?
On 07.09 11:46, Iljitsch van Beijnum wrote:
So then nothing stands in the way of adding AAAA glue records to the root?
Nothing other than the fact that the root is considered special by many and our collective processes are careful with changes to it. Some of this actually has rechnical rationale. I'll just name two examples: 1) The root servers are already the most loaded servers for any zone. 2) There are concerns that buggy resolvers may behave badly and aggrevate 1) above. So some more testing will have to be done and then the collective processes will have to run their course..... . Daniel
participants (2)
-
Daniel Karrenberg
-
Iljitsch van Beijnum