Last week I noticed that F root was showing poor connectivity with Indian RIPE Atlas probes for F-root. The graph looked really terrible.
Telekom Germany I traced to it from one of RIPE Atlas probes and saw this trace:
Probe #6107 1 2401:7500:fff0:1::1 0.838 ms 0.747 ms 0.632 ms 2 2400:5200:1c00:d::1 1.755 ms 1.745 ms 1.726 ms 3 2403:0:100::2be 2.089 ms 2.054 ms 2.049 ms 4 2404:a800:2a00::13d 45.589 ms 26.274 ms 33.
A few days some folks in internet community noticed Cloudflare AS13335 announcing F root server’s routes covering prefix 192.5.5.0/24. dig version.bind ch txt @f.root-servers.net pic.twitter.com/YLW7hqt170
— Tony Finch (@fanf) April 3, 2017 Above tweet shows that case is clearly not a mistake but rather some sort of arrangement between Cloudflare and ISC (which is responsible for F-root). There was another discussion on DNS-OARC mailing list here. From our bgp.he.net tool, one can analyse route propagation for F root’s AS3557.
Enjoyed ISC’s presentation about their analysis of F root server (one 13 root DNS servers which power the Internet) about anycast performance gloablly for 192.5.5.0/24 announced (and anycasted) by AS3557 (ISC). This was presentation at UKNOF 32.
Embedded presentation below (or click here to watch on YouTube directly)
Few days back I noticed F root server (which is with ISC) brought it’s anycasted node in NIXI Chennai back live. They have taken that down as per my interaction with them over mailing list. My last post about F root coming back live was with guess work on who’s providing upstream. Today I spent sometime in finding who’s providing transit to that node. It is very important to note that most of these key infrastructure related nodes rely on peering for most of traffic but a transit in form of full table or default stays so that one can push packets to a route if it is not in table learnt from peering.
And finally ACN i.e “Advanced Computer Networks” exam next. Hopefully less to cram in this one and syllabus is pretty interesting. Talking about networks - I am very happy to post this update. Finally F root server’s node in Chennai is back up! Though ISC did not updated me about this development but anyways I can always assume they were busy in hitting head with India bureaucratic bodies. :)
If you are following my blog, you might have seen my past blog post about “Broken connectivity of F root server” due to NIXI’s routing policies.