This evolution aims for increasing the confidence in DNS responses (by authenticating their origin); administrators of networks connected to Internet should be aware that this evolution could cause some service disruptions.
In fact, the changes in the root server configuration could lead to a DNS disconnection risk, and therefore disruption of Internet service in certain cases.
1. Check whether your network, as well as your DNS service, could be concerned by this potential dysfunction, on a machine where the dig software is set up:
dig +short rs.dns-oarc.net txt
2. Check that the response indicates more than 1500 bytes. For instance:
“203.0.113.1 DNS reply size limit is at least 4023 bytes”
3. Analyze the whole network and the intermediate equipments (firewalls), then make sure that everything has been properly configured, in case the tests indicate that the packets which are bigger than 1500 bytes can’t get through.
4. Another alternative, if you do not have a simple DNS client like dig:
This tool, developed by the RIPE-NCC, requires Java.
5. For end users (company, university or domestic ISP subscriber), please check with your ISP.
The DNS root is signed with the DNSSEC technology. In 2010, the root servers will start giving signed responses. From next May , the 13 root DNS servers will send the DNSSEC information. This includes cryptographic signatures, whose size is about five to ten times the standard DNS responses size. These signatures will exceed the DNS 512 bytes previous limit, and sometimes, even the 1500 bytes of the Ethernet MTU (“Maximum Transmit Unit�?), the most widely used on Internet.
In fact, RFC 2671, which extended the 512 bytes limit, was published in August 1999, and is more than ten years old. There are still some firewalls or other network equipments, which are badly designed or not properly configured, and will reject the DNS responses more than 512 bytes long.
Among the equipments which accept longer responses, some of them don’t correctly handle the IP packet fragmentation (For instance: because they may block all the ICMP packets) and therefore, they cannot receive DNS packets larger than the MTU (generally 1500 bytes).
Some of the networks which reject DNS packets larger than 512 bytes, or even the ones which only reject those longer than 1500 bytes, will no longer be able to “communicate�? with the DNS root after May 2010 (Indeed, this means that they will no longer get any response); and therefore, they will practically be unable to access to Internet
ROOT: the set of servers spread around the world, and upon which the domain names system relies. These servers have a key role in dispatching the requests to the right name servers of the relevant TLD (Top-Level Domain) such as .fr or.com.
Some useful links:
– The root signing plan announcement
– The official website for the signing project
– Instructions for a root server
– Can your DNS server accept any size packet (in French)?
– A French language mailing list about the DNS, where you can
get support from peers
(Association Française pour le Nommage Internet en Coopération )
Non-profit organization, AFNIC is in charge of the administrative and technical management of the .fr (France) and .re (Reunion Island) Internet domain names.
AFNIC brings together public and private members: representatives from the French government, Internet users and Internet Service Providers (Registrars).
Afnic is the acronym for Association Française pour le Nommage Internet en Coopération, the French Network Information Centre. The registry has been appointed by the French government to manage domain names under the .fr Top Level Domain. Afnic also manages the .re (Reunion Island), .pm (Saint-Pierre and Miquelon), .tf (French Southern and Antarctic Territories), .wf (Wallis and Futuna) and .yt (Mayotte) French Overseas TLDs.
In addition to managing French TLDs, Afnic’s role is part of a wider public interest mission, which is to contribute on a daily basis, thanks to the efforts of its teams and its members, to a secure and stable internet, open to innovation and in which the French internet community plays a leading role. As part of that mission, Afnic, a non-profit organization, has committed to devoting 11% of its Revenues from managing .fr Top Level Domain to actions of general interest, in particular by transferring €1.3 million each year to the Afnic Foundation for Digital Solidarity.
Afnic is also the back-end registry for the companies as well as local and regional authorities that have chosen to have their own TLD, such as .paris, .bzh, .alsace, .corsica, .mma, .ovh, .leclerc and .sncf.
Established in 1997 and based in Saint-Quentin-en-Yvelines, Afnic currently has nearly 90 employees.