Netnod’s anycast DNS: 20 years of 100% availability

14/03/2024

Netnod’s anycast DNS: 20 years of 100% availability

By Lars-Johan Liman, Senior Systems Specialist and co-founder at Netnod

Originally published in Netnod blog

Lars-Johan Liman, Netnod’s DNS nestor, makes a few personal reflections on the 20th anniversary of Netnod’s deployment of anycast – a technology that is a crucial part of the infrastructure of Netnod’s modern DNS services.

As stewards of one of the Internet’s 13 DNS root-server clusters, Netnod employs a technology called “anycast” to make our service available from a large number of locations across the world. Netnod (or to be precise, its then daughter company, Autonomica) was a pioneer of anycast technology, and this year marks the 20th anniversary of Netnod’s first anycast deployment.

On 22 August 2003, at 17:01 in the afternoon, I sent the historic message above to my fellow system administrators at all twelve root-server operators, after having just fired up instance number two of I-root. ‘Number one’ had been in operation for twelve years by then, but going from one to two instances was the major step, as that suddenly gave the routers on the Internet more than one path to the target. This sent ripples through the Internet’s routing fabric as the new instance of I-root was added to routing tables, BGP route selection algorithm came into play, and routers determined the best route to use, and to forward to their peers.

We chose to install the second server with our good friends at the Finnish Internet Exchange Point FICIX in ‘nearby’ Helsinki, Finland. Helsinki and Stockholm are a mere 400 km apart, but there is a troublesome amount of water in between, commonly referred to as the Baltic Sea.

At this time, Virtual Machines were not a well-known and reliable concept, so we had to install an entire stack of physical servers performing the different, necessary tasks.

(Free access, no subscription required)

The systems were mounted in a rack at the exchange point and furnished with power and network connections to handle the expected DNS traffic, and to receive management instructions remotely from Stockholm.

A lot of planning went into the network configuration and into preparing the network setup at the existing instance in Stockholm to deal with dual-instance operation. We also prepared new server infrastructure in Stockholm to handle data distribution of the DNS root zone. The root zone is the database that root-servers serve data from. It is updated twice per day, and now we needed our own distribution facilities to furnish two instances as opposed to just one. Our plans were to increase that number from two to 20 over the course of two to three years.

The server in Helsinki was first started without access to the exchange point. It could only talk to the ‘mothership’ in Stockholm. Using that channel it was loaded with correct data. The last pieces (except for the very last one) of the networking puzzle were laid and double-checked.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of LACNIC.

0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments