L-root node now hosted by MBIX

The story of how an L-root node came to be hosted by MBIX.

After meeting ICANN staff at NANOG 65 in Montreal, I started the process of getting an L-root node installed at MBIX.

First, I asked the Board to approve the cost of the hardware, which was about $2,800 CAD for the smallest server.

Next, I contacted ICANN and started the application process. There were forms to sign, mostly confirming that we would be a good host: keep the server powered on, connected to the network, and in a good facility.

After that, we exchanged technical details, mostly MBIX providing IP address information to the provisioning team.

Finally, the server arrived. We racked and powered it on, then the ICANN DNS engineering team completed the final configuration remotely to activate the server.

At that point, AS20144 was sending IPv4 and IPv6 prefixes over BGP to the MBIX router, not to the peering fabric or route servers. L-root does not peer directly at the exchange; it is hosted, so AS16395 needed to provide transit and peering on its behalf.

First, we started announcing the prefixes to the MBIX route servers. This worked well, and we started seeing queries using ICANN’s graphing tool at about 10–20 queries per second. Statistics can be viewed using ICANN’s tool.

Then, we announced the prefix to our upstream transit provider, Hurricane Electric (AS6939). This made no change because HE.net provides transit to AS20144 in Ashburn, Virginia, so the AS path to the MBIX node was longer and never preferred.

Then, we announced it upstream to Shaw (AS6327). This caused a large jump in traffic, up to 100 queries per second, but only on IPv6. Looking more carefully, I had mistyped my update request to Shaw and they had allowed the wrong prefix.

After Shaw corrected the mistake, we saw a flood of IPv4 queries to the YWG01 node: about 200 queries per second.

To test which L-root node you are getting results from, use dig:

dig CH TXT hostname.bind @l.root-servers.net

Use -4 or -6 to force the protocol version; you may get different results with each protocol.

MBIX is happy to be localizing DNS traffic and improving, in a small incremental way, the performance of the Canadian Internet.