Annual General Meeting

Thursday May 4th, 2017
3 to 6 p.m.
AGM to start at 3:30 p.m

King’s Head Pub
Open to all interested in IXs

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

Commstream joins MBIX

MBIX is pleased to announce our newest member Commstream (AS32773) is now connected to our peering fabric. This announcement is a bit late, they were operational the second week of February.

They’ve connected at 10 Gbps to the core switch at 167 Lombard. They’re peering with the route servers on IPv4 today, IPv6 in the future.

Commstream serves many rural Manitoban communities, mostly north of Winnipeg.  They offer internet service as well as TV and phone services over their coax plant.

It’s great to see another Manitoba ISP joining MBIX, taking active steps to improve internet infrastructure in Canada.

Verisign connects to MBIX

In partnership with MBIX, Verisign has connected to the MBIX peering LAN and has brought up its first IPv4 peering sessions, with IPv6 to follow soon.

Verisign is a major DNS operator, providing service to the largest TLDs .com, and .net.  The newly active server is part of their global infrastructure, and this Verisign RIRS Winnipeg node will provide very quick responses to MBIX-connected networks and their customers.  This server will answer queries for .com and .net names, as well as the root zone of DNS using the j.root-servers.net anycast name.

MBIX is providing space, power and management access to server, though the generosity of MBIX members.  Verisign has provided the hardware, and will manage the service, at no cost to MBIX.  DNS is used by nearly all internet services, and interruptions in the DNS can cause major outages. This collaboration will result in better performance for internet users in Manitoba, and also provide more resilience in the face of natural disaster or denial-of-service attacks.

Welcome to Canada, Verisign, hope to see you at more Canadian IXPs soon!

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, 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 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.