Day before yesterday i.e on 18th August 2016 Bangladesh’s TLD .bd went had an outage. It was originally reported by Jasim Alam on bdNOG mailing list. dig btcl.com.bd @22.214.171.124 ; <<>> DiG 9.10.4-P2 <<>> btcl.com.bd @126.96.36.199 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 8114 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;btcl.
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.
It has been an interesting week at village - dry weather, (ultra) dry classes, (boring) external seminars and more of depressing environment but one can always find some hope out of such depressing environment. Overall life here is colourful but one just needs to lookout for colours. :) One interesting case to report today - F root server has quite bad connectivity in India. Last week a friend asked me for traceroutes to all root servers and here’s what I saw when I did traceroute for F root from BSNL connection: