I'm not sure if this is the right place to post this, but here 'goes: Earlier today I moved a site from my old shared-host to my own dedicated server. I went to my registrar and changed the nameservers to my dedicated server, and after about 2 hours, http://mysite.com was resolving to the new server, but now after 6 hours or so, www.mysite.com is still resolving to the old host. is this normal, or have i skrewed up something?
Are you getting authoritative data back or cached ? Have you cleared your local resolver cache? You said it was resolving correctly earlier. Have you changed anything since then?
This is my look of "i have no idea what you're talking about" .. clearly i am a n00b, so you may have to talk slower. It's still resolving properly to http://mysite.com (goes to new server) .. but if i put www in front; http://www.mysite.com it's going to my old host..
i have the host record in the server DNS.. and if you were referring to my local PC's cache in your previous post, i have flushed that.. when i do an NSLOOKUP, it shows "non authorative answer:" it's correct for http://mysite.com but shows my old host for http://www.mysite.com
and here's another weird thing: all day, when pinging http://mysite.com it's been showing the new server and when pinging www.mysite.com, the old server NOW, after i did an NSLOOKUP, pingining it both ways is showing the OLD server again.. either i'm going crazy or something odd going on.. is this normal??
Ok, then it is probable that the DNS you are using to get your non-authoritative answer is sending back data whose TTL has yet to expire and therefore sends back your old DNS info. A tool like this might give you an authoritative lookup: http://www.geektools.com/digtool.php Does it say your old host for www. ?
i found the problem.. I'm not sure how, but the nameserver on the new server was pointing to the old host's nameserver.. I pointed the nameserver to "itself" basically, and all is good now..