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 $2800 CAD (For the smallest server).

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

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

Finally, the server arrived, we racked it, and powered it on.  The ICANN DNS engineering team did final configuration remotely to activate the server.

At that point, we had AS20144 sending v4 and v6 prefixes over BGP, to the MBIX router (not to the peering fabric or route servers). L-root doesn’t peer directly at the exchange, they are hosted, so AS16395 needed to provide transit and peering on their behalf.

First, we started announcing the prefixes to the MBIX route servers.  This worked well, and we started seeing queries coming in using ICANN’s graphing tool, about 10-20 qps. Stats can be viewed using ICANN’s tool: http://stats.dns.icann.org/hedgehog/hedgehog.html

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.  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 qps.  But the increase was only on IPv6.  Looking more carefully, I had typo’d my update request to Shaw, and they had allowed the wrong prefix.

I had Shaw correct the mistake, and once they did we saw a flood of IPv4 queries to the YWG01 node, about 200 qps.

To test which L-root node you’re getting results from, you can use the ‘dig’ too:

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

You can use -4 or -6 to force the protocol version–you may get different results with each protocol. I’d be interested in knowing your results.

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

Annual General Meeting

Wednesday May 4th, 2016
4 to 6 p.m.
AGM to start at 4:30 p.m

King’s Head Pub
Open to all interested in IXs

There are 4 Board of Director positions open for election.
Jacques Latour from CIRA will give an update on Canadian IXs.

Social time before and after the meeting with drinks and snacks provided by CIRA and MBIX.



After working hard to get all the technical details right, we can announce that HBNI (AS31914) is the newest connected MBIX member.

They’re connected at 1 Gbps at the 167 Lombard location.  They’re peering with the route servers on IPv4, and working on full IPv6 peering in time.

HBNI serves Hutterite colonies throughout rural Manitoba, with a focus on education.  Having their network directly connected to MBIX will serve to increase the performance of this specialized ISP, and keeps more data within Manitoba, lowering outside costs.

Quickstream Internet joins MBIX

Last week the finishing touches were completed on our newest member connection.

Quickstream Internet, a Manitoba WISP, is now connect to MBIX and peering on IPv4 and IPv6.  They’re plugged into to our switch at 167 Lombard at 10 Gbps.

This bring our connected peer count to 20. That means there are now 20 independent networks connected to MBIX, which is a nice milestone.

It’s great to have more Manitoban networks connecting to MBIX, traffic levels are now reaching 600 Mbps on the average day–all this represents data not flowing to via expensive long haul links to the United States or Toronto, or through the expensive large telcos.  Keeping data local is definitely good for Manitoba.