I wish I could say I don’t care about airtel.in, but because they are my ISP, I have to care :(.
The genius people at airtel.in CNAME-d the root record of their zone. 🙁
λ drill -t ns airtel.in @aaadel.mantraonline.com ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 55824 ;; flags: qr aa rd ra ; QUERY: 1, ANSWER: 3, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;; airtel.in. IN NS ;; ANSWER SECTION: airtel.in. 28800 IN CNAME www.airtel.in. www.airtel.in. 7200 IN CNAME airtel.in.edgekey.net. airtel.in.edgekey.net. 19572 IN CNAME e8827.a.akamaiedge.net. ;; AUTHORITY SECTION: a.akamaiedge.net. 572 IN SOA n0a.akamaiedge.net. hostmaster.akamai.com. 1481797738 1000 1000 1000 1800 ;; ADDITIONAL SECTION: ;; Query time: 46 msec ;; SERVER: 18.104.22.168 ;; WHEN: Thu Dec 15 16:06:06 2016 ;; MSG SIZE rcvd: 174
Some less-strict resolvers seems to work with them, but others don’t. I mailed them (the WHOIS contact address) a month or two ago, but seems like it went to /dev/null. Today, when I went to access their looking glass, it again bit me. For now, I added
lg.airtel.in to my
hosts(5) file, where it will live, until it breaks.