Does my WRT54G hate Godaddy Hosted websites?

July 17, 2010 3:56 PM

I am having connectivity issues with Time Warner, WRT54G and Godaddy hosting , but exclusively to godaddy hosted sites.

This is a pretty specific connection issue i hope someone can help me with. I have Time Warner Broadband service at home connected to a Linksys WRT54G Router, and its been working flawlessly for over 6-7 years. For some reason, this past week, i have been unable to reach ANY godaddy hosted websites, but have been able to reach any other site i can think of, and i know those sites are up, since they are accessible by everybody else:

http://www.etropa.com
http://www.unify.org
http://proxygaming.com

(three different hosting plans from godaddy) You probably can reach them ok.

Ive done the resetting of the router, i even updated my firmware to a custom firmware out of desperation (Tomato V1.28) and everything works, except connecting to the godaddy websites. So total router reset, NVRAM reset doesnt clear up the problem.

Name resolves to ip, I cant ping, i cant connect to them via FTP, traceroute fails after the 14th hop or so, again, just to those godaddy sites.

The odd thing is that if i connect my PC directly to the cable modem, websites pull up fine, so it would seem to be something on the router is preventing me from connecting to those sites.

(I tried fiddling with the MTU, but not sure if thats the culprit)

Godaddy and my ISP shrugs and says must be my router.

Any network techs/gurus can give me some/any pointers? Ive been banging my head on this issue for the past few days, and my forehead is pretty flattened at this point. Can a router 'go bad?' just to godaddy?

posted by edman to Technology (6 answers total)

Best answer: This is definitely odd.

Run a traceroute to one of the problem sites with and without the router. Look to see where they differ. If you can post them both, that would be even better.

One thing you didn't cover in the original post is whether the hosts resolve to the CORRECT ip address. This is what I get (checked to be identical between google dns (8.8.8.8) and a root server (4.2.2.2):

proxygaming.com has address 173.201.148.128
unify.org has address 97.74.215.81
etropa.com has address 97.74.215.157


You should also check to see if they're resolving to the same IP in both scenarios, and if so trace down which DNS servers you're using in each instance. Does your router get them from upstream or are they hard-coded? For that matter, does your PC get it's dns server list from your router, or is it hard coded? The three domains you list as examples all use DOMAINCONTROL.COM nameservers - so that might be the commonality (rather than the web hosting which would make less sense)



One more test (which would prove/disprove my shot-in-the-dark theory above): set your computer's nameserver to 8.8.8.8 and see if the problem persists.
posted by devbrain at 4:06 PM on July 17, 2010

Response by poster: hi devbrain!

Yes, I have been using google's dns for a while (8.8.8.8, and 8.8.4.4). The dns resolves properly from behind the router and matches the numbers you posted. I have a pc that i have hard coded the ip and dns also.

But i did come across something odd when I did a compare between tracert from behind the router and one directly to the modem.

When i was behind the router, nslookup to www.etropa.com returned the correct response: Non-authoritative answer:
Name: etropa.com
Address: 97.74.215.157

But, when i plugged it into the modem, the dhcp assigned me to a new dns (rdns-lb-01.hawaii.rr.com) and when i did a nslookup:

Non-authoritative answer:
Name: www.etropa.com.hawaii.rr.com
Address: 24.28.193.9

but when i tracert it resolved to the proper 97.74.215.157 ip and was successful, and i could pull the website up.

For chuckles, I hardcoded rdns-lb-01.hawaii.rr.com ip as my dns behind the router, and it resolved properly and did not resolve to that odd 24.28 address, but still did not ping, pull up.

Including tracert and nslookup log:
-----------------------------------------------------------
(behind the router)

C:\Users\edyagi>nslookup
Default Server: google-public-dns-a.google.com
Address: 8.8.8.8

> www.etropa.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: etropa.com
Address: 97.74.215.157
Aliases: www.etropa.com

> quit

C:\Users\edyagi>tracert www.etropa.com

Tracing route to etropa.com [97.74.215.157]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 12 ms 9 ms 7 ms 10.100.160.1
3 10 ms 17 ms 9 ms ge10-0-9-oahuhimili-gsr2.hawaii.rr.com [24.25.22
4.174]
4 13 ms 9 ms 10 ms pos0-1-oahuhimili-gsr1.hawaii.rr.com [24.25.229.
165]
5 10 ms 11 ms 11 ms ge-2-0-0-oahuhimili-rtr1.hawaii.rr.com [24.25.22
4.138]
6 59 ms 60 ms 61 ms xe-6-1-3-tustca1-rtr1.socal.rr.com [24.25.230.13
0]
7 69 ms 61 ms 60 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
8 68 ms 157 ms 65 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
9 144 ms 65 ms 69 ms 66.109.9.206
10 95 ms 95 ms 103 ms 64.209.110.218
11 74 ms 76 ms 74 ms ip-208-109-112-153.ip.secureserver.net [208.109.
112.153]
12 75 ms 73 ms 73 ms ip-208-109-112-142.ip.secureserver.net [208.109.
112.142]
13 76 ms 74 ms 72 ms ip-216-69-188-77.ip.secureserver.net [216.69.188
.77]
14 * * * Request timed out.
15 * * ^C

------------------------------
(connected directly to the modem)

C:\Users\edyagi>nslookup
Default Server: rdns-lb-01.hawaii.rr.com
Address: 24.25.227.55

> www.etropa.com
Server: rdns-lb-01.hawaii.rr.com
Address: 24.25.227.55

Non-authoritative answer:
Name: www.etropa.com.hawaii.rr.com
Address: 24.28.193.9

> quit

C:\Users\edyagi>tracert www.etropa.com

Tracing route to etropa.com [97.74.215.157]
over a maximum of 30 hops:

1 9 ms 7 ms 9 ms 10.100.160.1
2 8 ms 10 ms 14 ms ge10-0-9-oahuhimili-gsr2.hawaii.rr.com [24.25.22
4.174]
3 9 ms 10 ms 9 ms pos0-0-oahuhimili-gsr1.hawaii.rr.com [24.25.229.
161]
4 10 ms 10 ms 9 ms ge-2-0-0-oahuhimili-rtr1.hawaii.rr.com [24.25.22
4.138]
5 67 ms 66 ms 70 ms xe-4-0-3-tustca1-rtr1.socal.rr.com [24.25.230.13
4]
6 65 ms 62 ms 63 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
7 60 ms 127 ms 144 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
8 59 ms 65 ms 59 ms 66.109.9.206
9 78 ms 112 ms 123 ms 64.209.110.218
10 72 ms 72 ms 70 ms ip-208-109-112-153.ip.secureserver.net [208.109.
112.153]
11 71 ms 72 ms 69 ms ip-208-109-112-142.ip.secureserver.net [208.109.
112.142]
12 69 ms 69 ms 68 ms ip-216-69-188-77.ip.secureserver.net [216.69.188
.77]
13 71 ms 73 ms 71 ms ip-216-69-188-102.ip.secureserver.net [216.69.18
8.102]
14 70 ms 71 ms 71 ms p3nw8sh133.shr.prod.phx3.secureserver.net [97.74
.215.157]

Trace complete.

------------
any help appreciated!
posted by edman at 6:04 PM on July 17, 2010

Best answer: Ah, you found it! rdns-lb-01.hawaii.rr.com has old info and needs to update. The issue will probably go away in the next day or two.
posted by goblinbox at 6:13 PM on July 17, 2010

Response by poster: goblinbox, so even though i dont use rdns-lb-01, its incorrect entry will mess my connection/routing up to godaddy? this has been happening for the past 3-4 days, is this something that RR should be able to address?
posted by edman at 6:41 PM on July 17, 2010

Response by poster: Hm. after updating to Tomato Firmware, it allowed me to change my mac address, which forced my RR to give me a new IP, and as soon as that happened, godaddy started working.

Thanks to galinbox, devbrain,
posted by edman at 2:07 AM on July 18, 2010

Very odd -- glad it's all fixed.
posted by devbrain at 6:42 AM on July 18, 2010