M-Root deployment to expand under new collaboration agreement

By on 31 Aug 2020

Categories: Development Tech matters

Tags: ,

Blog home


The WIDE Project, Japan Registry Services (JPRS) and APNIC will work together to expand M-Root DNS services in the Asia Pacific and beyond after signing a Memorandum of Understanding (MoU).

The WIDE Project, which has served as the Root Server Operator (RSO) for M-Root since 1997, is one of just 12 operators globally and the only one based in the Asia Pacific. There are currently nine M-Root instances located in Japan, South Korea, France and the United States.

JPRS, jointly with the WIDE Project, has operated and deployed M-Root instances since December 2005. By acting as a part of the RSO, JPRS tries to give a better experience of both the Root DNS and .jp DNS to the Internet community.

APNIC has supported the deployment of DNS root server instances throughout the region since 2000, and has supported 32 anycast deployments by five Root Servers, including F-Root, I-Root, K-Root and now M-Root. APNIC also operates critical reverse DNS infrastructure for its Members with Domain Name System Security Extensions (DNSSEC) support.

By working together, the WIDE Project, JPRS and APNIC will greatly expand M-Root’s footprint throughout the region to improve DNS reachability, resilience and response times for Asia Pacific ISPs and end users. Increased root server distribution provides higher performance DNS lookup, independent of the user’s location, as the request can be dealt with by a closer instance of the nameserver.

New M-Root instances established under the MoU will prioritize major Internet interconnection locations as well as underserved locations, with hosts such as diverse IP transit providers and carrier-neutral Internet Exchange Points (IXPs).

The first new instance will be deployed within APNIC’s facilities in Brisbane, Australia, and provide public service by the end of 2020.

Rate this article

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

Leave a Reply

Your email address will not be published. Required fields are marked *