eNom DNS resolution problem

Dns, Networking

Boring exam days, anyways time for a quick blog post to keep taste in life. :)

One of my good friend informed me about eNom DNS servers failing randomly. He gave clothdiaperrevival.com as sample domain name for testing.


Quick Check from my home connection:

anurag@laptop ~ $ dig clothdiaperrevival.com a @dns1.name-services.com +short  
216.239.32.21  
216.239.34.21  
216.239.36.21  
216.239.38.21

anurag@laptop ~ $ dig clothdiaperrevival.com a @dns2.name-services.com +short  
216.239.36.21  
216.239.32.21  
216.239.38.21  
216.239.34.21

anurag@laptop ~ $ dig clothdiaperrevival.com a @dns3.name-services.com +short  
216.239.38.21  
216.239.34.21  
216.239.32.21  
216.239.36.21

anurag@laptop ~ $ dig clothdiaperrevival.com a @dns4.name-services.com +short  
216.239.32.21  
216.239.38.21  
216.239.34.21  
216.239.36.21

anurag@laptop ~ $ dig clothdiaperrevival.com a @dns5.name-services.com +short  
216.239.32.21  
216.239.34.21  
216.239.36.21  
216.239.38.21

Next, checking from my EU located server:

anurag@server7:~$ dig clothdiaperrevival.com a @dns1.name-services.com +short  
216.239.32.21  
216.239.34.21  
216.239.36.21  
216.239.38.21

anurag@server7:~$ dig clothdiaperrevival.com a @dns2.name-services.com +short

anurag@server7:~$ dig clothdiaperrevival.com a @dns3.name-services.com +short  
216.239.36.21  
216.239.38.21  
216.239.32.21  
216.239.34.21

anurag@server7:~$ dig clothdiaperrevival.com a @dns4.name-services.com +short  
216.239.32.21  
216.239.38.21  
216.239.36.21  
216.239.34.21

anurag@server7:~$ dig clothdiaperrevival.com a @dns5.name-services.com +short  
216.239.32.21  
216.239.34.21  
216.239.36.21  
216.239.38.21

dns2.name-services.com is failing when reached my EU based server.


Quick check again to confirm:

anurag@server7:~$ dig clothdiaperrevival.com ns @**dns2.name-services.com**

; <<>> DiG 9.7.3 <<>> clothdiaperrevival.com ns @dns2.name-services.com  
;; global options: +cmd  
;; Got answer:  
;; ->>HEADER<<- opcode: QUERY, **status: NXDOMAIN**, id: 43272  
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0  
;; WARNING: recursion requested but not available

;; QUESTION SECTION:  
;clothdiaperrevival.com. IN NS

;; AUTHORITY SECTION:  
com. 3601 IN SOA dns1.name-services.com. info.name-services.com. 2010 10001 1801 604801 181

;; Query time: 172 msec  
;; SERVER: **98.124.197.1**#53(98.124.197.1)  
;; WHEN: Tue Jul 3 19:02:35 2012  
;; MSG SIZE rcvd: 100

Yes NXDOMAIN - not holding delegation at all.

The anycasted IP which on which server is failing is - 98.124.197.1

IP is coming from - 98.124.197.0/24 announced by AS 21740 by eNom.


Quick look at Global routing table for that block:

route-views>show ip bgp 98.124.197.0/24 long  
BGP table version is 127262564, local router ID is 128.223.51.103  
Status codes: s suppressed, d damped, h history, \* valid, > best, i - internal,  
r RIB-failure, S Stale  
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path  
* 98.124.197.0/24 4.69.184.193 0 0 3356 **3257** 21740 i  
* 208.74.64.40 0 19214 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 202.249.2.86 0 7500 2497 3257 21740 i  
* 194.85.102.33 0 3277 3267 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 154.11.98.225 0 0 852 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 154.11.11.113 0 0 852 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 217.75.96.60 0 0 16150 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 195.66.232.239 0 5459 2828 26769 21740 21740 21740 21740 21740 21740 i  
* 209.124.176.223 0 101 101 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 64.71.255.61 0 812 174 26769 21740 21740 21740 21740 21740 21740 i  
* 194.85.40.15 0 3267 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 66.59.190.221 0 6539 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 69.31.111.244 3 0 4436 2828 26769 21740 21740 21740 21740 21740 21740 i  
* 65.106.7.139 3 0 2828 26769 21740 21740 21740 21740 21740 21740 i  
* 208.51.134.254 2 0 3549 3257 21740 i  
* 144.228.241.130 0 1239 3257 21740 i  
* 129.250.0.11 10 0 2914 3257 21740 i  
* 193.0.0.56 0 3333 3257 21740 i  
* 134.222.87.1 0 286 3257 21740 i  
* 207.172.6.20 0 0 6079 3257 21740 i  
* 157.130.10.233 0 701 3257 3257 21740 i  
* 207.46.32.34 0 8075 3257 21740 i  
* 207.172.6.1 0 0 6079 3257 21740 i  
* 66.185.128.48 7 0 1668 3257 21740 i  
* 203.62.252.186 0 1221 4637 174 26769 21740 21740 21740 21740 21740 21740 i  
*> 89.149.178.10 10 0 3257 21740 i  
* 202.232.0.2 0 2497 3257 21740 i  
* 12.0.1.63 0 7018 3257 21740 i  
* 216.218.252.164 0 6939 2828 26769 21740 21740 21740 21740 21740 21740 i  
* 206.24.210.102 0 3561 3257 21740 i  
* 66.110.0.86 0 6453 3257 21740 i  
* 114.31.199.1 0 0 4826 12989 26769 21740 21740 21740 21740 21740 21740 i  
* 128.223.253.10 0 3582 4600 11164 12989 26769 21740 21740 21740 21740 21740 21740 i  
route-views>

Thus anycasting for sure (you see multiple AS in 2nd last). One of instances sitting below Tinet 3257 is failing. The border router IP 69.64.152.78 below which one of their anycasted DNS server is placed is failing. It is NOT a networking related glitch, but rather DNS server problem which is missing delegation for few domain names.

Hope eNom folks will fix it soon!