Domain Not Resolving through my ISP

March 3, 2008 8:18 PM

My domain is resolving for others to see, but not me !

HELP! One of my domains, CLIKT.com, is registered at GoDaddy and now hosted at Hostgator.

When I enter the domain's URL in a browser (Firefox or IE - doesn't matter) I see an old screen with the cash parking page from GoDaddy even though the nameservers have been updated. When I ask others to look at the site, they report no problems and the site renders as it should. (Right now I've left the site empty so all that should be displayed is the directory listing.) I've waited days and not seen the actual site as I should. I've tried clearing my browser cache as well as running CCleaner to remove any trace of the incorrect pages.

I've also had the same issue when I had the domain hosted at another provider. (The site looks like the cash parking page on my end, but looks fine to others or if i view the site through Proxify.)

And the strange thing is, I have about 25 domains registered with GoDaddy and hosted at various spots, but this is the only one that is affected.

My ISP is AT&T (I have a DSL account that I use and through which I am seeing the old site). I am not sure if the problem is with them or GoDaddy (since I have other domains registered there that are hosted at HostGator and other places without issue). A tech at GoDaddy reported that he could see the site so the problem was probably with the ISP (AT&T) but I'm not sure about that and why other domains wouldn't be affected....

So is the problem with the ISP or with the registrar ?

I'm half-tempted to transfer the domain to another registrar to see if that solves the problem, but that doesn't tell me what the cause is, only the source....

ATT version: http://www.joejurczyk.com/CLIKT-ATT.jpg
Proxify version: http://www.joejurczyk.com/CLIKT-Proxify.jpg

Sorry for babbling on....thanks for listening

posted by jurczyk to computers & internet (8 comments total)

Have you tried entering the site's numerical IP address? Or deleting any cookies from Go Daddy?
posted by words1 at 8:26 PM on March 3, 2008

Change your DNS to verizon's 4.2.2.1. Does that clear it up?

Sounds like AT&T isnt updating their DNS as quickly as you would like them to.
posted by damn dirty ape at 8:36 PM on March 3, 2008

it appears the records were only updated today. perhaps at&t's dns servers have not yet picked up the update. some places say that can take up to three days. if the proxify version works obviously the site it up. give the records time to propagate and check tomorrow. if the problem persists maybe try different dns servers such as opendns

btw those pictures dont show up for me
posted by DJWeezy at 8:50 PM on March 3, 2008

Refresh your DNS cache. In Windows, Start -> Run, "ipconfig /flushdns". For OS X and Linux, click here.
posted by spiderskull at 9:24 PM on March 3, 2008

Maybe a unlikely answer, but you could also check your hosts file (found in C:\WINDOWS\system32\drivers\etc\).

If you've been playing with it, your entries there would override any DNS entry for you and only you.
posted by razdrez at 10:32 PM on March 3, 2008

If none of the above answers worked for you, you can query your nameserver directly to see if it has the right values. At a command prompt, type "nslookup". You should then receive a prompt; you can then type the name you want to resolve. Use a fully-qualified name so there's no confusion: "www.yourserver.com." (The period at the end is to let it know that's the root, rather than a subdomain prepended to your default domain suffix.)

If the name doesn't resolve, it's a problem with the nameserver your computer is asking. Try other nameservers by entering "server someothernameserver.somedomain.com", then asking that server for the same fully-qualified name.
posted by me & my monkey at 2:51 AM on March 4, 2008

As DJWeezy says, domain changes can take a while to propagate. In theory this is controlled by the TTL records (Time To Live) which states how long the information is good for. However bigger ISP's sometimes have a habit of ignoring TTL records, particularly if they are set short, to avoid having to refresh their cached DNS records all the time.

You are not the only one complaining about AT&T's dns servers, it appears, you could try Open DNS as an alternative.

You appear to have bigger problems with joejurczyk.com -- the NS (name server) records point to ns1.jaite.net & ns2.jaite.net which don't have any DNS records, so for all intents and purposes don't exist. You need to get the records to point to new name servers. (via GoDaddy or whoever you registered it with).
posted by tallus at 3:12 AM on March 4, 2008

Thanks everyone for your suggestions. I tried several including ipconfig/dnsflush, changing the settings on the Hosts file and deleting all of my cookies. (Also got a suggestion elsewhere to restart the modem.) Though none of the solutions worked immediately, this morning the site renders for me fine. So, problem solved (though I don't exactly know how.)

Thanks again !

Joe

P.S. thanks for the info about JoeJurczyk.com - jaite.net is a custom nameserver I have setup at eNom but I'm also planning on moving the site to my GoDaddy account and moving the hosting to HostGator
posted by jurczyk at 5:09 AM on March 4, 2008