“On 4 February 2008, IANA will add AAAA records for the IPv6 addresses of the four root servers whose operators have requested it.”
ICANN (Internet Corporation for Assigned Names and Numbers) is responsible for the global Domain Name System, IANA ( Internet Assigned Numbers Authority ) is a part of ICANN. So as this article states, “come February 4, 2008, it will be possible for two IPv6 hosts to communicate across the IPv6 Internet without having to rely on any IPv4 infrastructure.”
We’ve heard a lot of stories about getting to this point for several years now and I’m happy to see that it’s finally coming together.
Just as the article explains, when a DNS server starts up, it has to find the root servers that sit at the top of the name delegation chain. For this purpose, a DNS server keeps a local hints file, named.root, (or named.cache or named.ca, found in /var/named/ on many systems) that has the names and addresses for all the root servers. However, system administrators don’t always keep this file up to date, so the first thing that a DNS server does upon startup is ask for an up-to-date list of root servers. So as long as there is still a single correct root server address in that named.root file, everything will work.
The problem: the original Domain Name System specification only allows for 512-byte packets in the DNS protocol. Now doing the math with 13 root servers, that’s quite a bit over 400 bytes already. Now if you wanted to have any useful number of IPv6 addresses for root servers it would push this beyond the 512-byte limit. This is part of the reason that the parties involved have constantly re-evaluated the downside effects.
The majority of modern DNS software is very well capable of sending and receiving packets larger than 512 bytes. If a DNS server doesn’t indicate this capability in its request, the root server will fit as much as it can within a 512-byte packet and mark the answer as “truncated,” which is the requester’s cue to retry the request over TCP rather than the usual UDP. So older DNS software shouldn’t have any problems, either, so long as firewalls don’t block DNS packets larger than 512 bytes or DNS requests over TCP.
Filed under: Co-location, Hosting | Tagged: Byte, DNS, IANA, ICANN, Infrastructure., Internet, IP Address, iPv6, Network, PEER 1, Protocol, Root, Self-managed hosting, server, Technology, Unmanaged hosting |