Running your own Root Name Server

From Wikipedia, the free encyclopedia

Edit - Copy icon This page is a candidate to be copied to Wikibooks using the Import process.
If the page can be re-written into an encyclopedic article, please do so and remove this message.

Before you move this content to Wikibooks, verify that it conforms to Wikibooks policies of acceptable content at What is Wikibooks?. Often content unacceptable to Wikipedia may not be acceptable on Wikibooks either; facilitate the copying of this article by listing it on Wikibooks:Requests for Import.

In addition to the Internet's main DNS root, it also possible to organize and run your own root nameservers and with the officially sanctioned root zone file.

While the Internet Architecture Board has spoken out strongly against alternate roots in RFC 2826, "IAB Technical Comment on the Unique DNS Root", to date there is little public comment on the concept of localized root by people other than the current root server operators. To date, only the operator of I-ROOT has commented on localized root servers.

There are many operational issues to address in operating your own localized root server. One would be routing the answers back to your localized server. Along with the concept of using routing based RBL's or blacklists, one can redirect a packet for a root server, much in the same way that current network operators redirect packets for spam and abuse oriented address, and designate a local platform to answer that resource request. This special configuration would allow an entity to assign servers A-M locally so that all traffic would query a locally managed root server. The routing could be configured to anycast the cloned resources internally and allow for failover to the external resources.

The difference between this and an Alternative Root system is that this system defers to the US DOC authorized zone file vs. an altered, unofficial, root zone file.