K root in Noida seems to be not getting enough traffic from quite sometime and connectivity does seems bit broken. This is a blog post following up to Dyn’s excellent and detailed post about how TIC leaked the world famous 193.0.14.0/24 address space used by AS25152. It was good to read this post from RIPE NCC written by my friend Emile (and thanks to him for crediting me to signal about traffic hitting outside!)
Super dull time here. No classes going on due to “TCS Placement session” at college and this makes me to sit in my room most of time of my day.
Yesterday I tested connectivity to all 13 Global Root DNS Servers and found i root was giving issue.
Here’s a my yesterday’s traceroute to i root:
traceroute to i.root-servers.net. (192.36.148.17), 30 hops max, 60 byte packets
1 router.local (10.0.0.1) 1.470 ms 1.965 ms 2.452 ms
2 117.200.48.1 (117.200.48.1) 26.030 ms 28.857 ms 31.243 ms
3 218.248.173.46 (218.248.173.46) 34.673 ms 37.091 ms 41.025 ms
4 218.248.246.130 (218.248.246.130) 72.853 ms 75.272 ms 77.959 ms
5 * * *
6 * * *
Since i root is another root server hosted within India by NIXI, I was quite sure this was issue again due to NIXI’s regional route enforcement policy along with missing transit link on i root. You can see my last blog post about same issue with F root here.
Time for a quick followup blog post. On 26th April of this year I blogged about broken connectivity of F root server which was hosted in NIXI Chennai. Apart from that blog post, I did informed ISC which operates F root (NIXI was host on behalf of them in India). In my open email on APNIC mailing list, I got a reply from Network Operations Center of ISC that they will verify and will take necessary action. Within 48 hours of that email they figured out root cause and since they couldn’t fix it right at that point, they pulled plug off from that root server.
In last few days, I have been pushing discussion on APNIC & NANOG mailing lists about poor DNS infrastructure in India.
Thought to put a quick blog post on the issue.
So what’s exactly wrong?
To understand what’s wrong, let’s understand how DNS works at core level. DNS relies on a hierarchy model with . (dot) on top which is Root and TLD i.e Top Level Domains below Root, which further follow 2nd level domains which are popularly domain names we use. So e.g mail.google.com is actually like
Today I was showing a good friend - how root servers are working and how they are connected. I was explaining him anycasting and gave example of k-root node which is hosted in Delhi by niXi i.e National Internet Exchange of India. I was totally stunned to find traceroute result to anycasting based block of k-root-node hosted in Delhi from my BSNL connection. Checkout traceroute here.
It seems like BSNL has gone totally wild in listening to announcements for 193.0.14.0/23 via ASN 25152 which is of RIPE-NCC-K-ROOT nodes.