Root server - FAQs
- Which root servers are involved?
- Will new root server "letters" be allocated?
- What is "BGP Anycast"?
- Will the new servers be fully operational root servers?
- Is there a difference between the different "letters"?
- Are "anycast" servers different from the "real" servers?
- Will APNIC become a "Root Server Operator"?
- Why is APNIC involved?
- Will APNIC continue to support root servers in future?
- Where are root servers being deployed?
Which root servers are involved?
APNIC has formal MoU agreements with the operators of the F-Root and the I-Root, and is also cooperating actively with K-Root and M-Root. The organizations involved are as follows:
| F-Root | ISC, the Internet Systems Consortium, a US non-profit organization that
is responsible for BIND and other widely-used Internet server software,
including DHCP and INN. |
| I-Root | Autonomica AB, a Swedish technical support company working in the
fields of the Domain Name System, email, and Internet exchange point
technologies. |
| K-Root | RIPE NCC, the Network Coordination Centre of RIPE, which is APNIC's counterpart RIR in the European region. |
| M-Root | WIDE Project of Japan, a key research and development institution in the areas of Internet applications, IPv6, and related technologies. |
Will new root server "letters" be allocated?
No. Rather than requiring new root server identifiers (such as A,B,C,...M), the BGP anycast technique will allow the existing root servers to be copied across multiple separate servers located at different points on the Internet.
What is "BGP Anycast"?
BGP Anycast It is a technique whereby the same address space is used and announced in the normal way but from multiple locations on the Internet. Within the BGP routing system, multiple routes to the same address space will be seen, and the shortest route is given preference in the normal way.
BGP Anycast is well tested and has been in use for many years in appropriate services such as DNS. It is suitable for transaction-oriented services, such as DNS or whois, but not for connection-oriented services, which require a long-term connection between a client and a particular server.
For more information, see:
- RIPE-268, "Distributing K-Root Service by Anycast Routing of 193.0.14.129"
- ISC's Technical Note 2003-1," Hierarchical Anycast for Global Service Distribution"
Will the new servers be fully operational root servers?
Each of the supported sites will provide a fully operational root server.
Is there a difference between the different "letters"?
There are differences between servers in terms of hardware, software, and operational practices; however, there is no hierarchy of status or importance among the servers. Each of the 13 separate rootservers (that is, from A-Root to M-Root) behave identically in DNS terms and are distinguished only by their different "letter" names and IP addresses.
Are "anycast" servers different from the "real" servers?
No. When anycast distribution of an existing server is implemented, all servers become 'anycast servers', including the 'original' server. All anycast instances behave identically and have the same status within the DNS.
Will APNIC become a "Root Server Operator"?
No. The existing root server operators will maintain full and exclusive administrative control over all copies of their servers. APNIC's contribution is to locate suitable sites, and provide the equipment.
Why is APNIC involved?
While APNIC is not involved in domain name registrations, the DNS carries several critical infrastructure services, including reverse DNS trees, in-addr.arpa and ip6.arpa. We have been asked many times to take some involvement in root server operations to improve access to these infrastructures for ISPs in the Asia Pacific region.
APNIC's role in root server operations is as a voluntary facilitator and coordinator of root server deployments in this region.
Will APNIC continue to support root servers in future?
After the first trial year of this project, it is apparent that the availability and efficiency of root services has greatly improved in many parts of the Asia Pacific region. The project will continue to deploy new servers in future where demand exists.
Where are root servers being deployed?
During the first year of this project, servers were installed in many locations, including Hong Kong, Seoul, Beijing, Taipei, Singapore, and Brisbane.
Additional sites may be proposed by responding to the existing call for expressions of interest.