| Posted by kenfused, 03-12-2008, 02:42 PM | | Hello,
I'm having an odd problem.
On my home computer if I ping mysite.com I get 207.210.88.88 which is the correct site pointing to my site at http://207.210.88.88/~username/
However, on other computers at different locations I sometimes get 216.180.231.76 which is my OLD server
Last summer I moved servers and since then I have noticed that sometimes I get the old site, sometimes the new one. My site was moved last summer within the same hosting company
I have updated the DNS servers at my registrar (namecheap) to my latest assigned nameserver ns120a.genericdns.com and ns120b.genericdns.com (as assigned) and that did not seem to help! I also tried switching my DNS back to the old server for 12 hours, then switching back to the new ones (above) but I'm still getting the old site sometimes.
Why are there 2 versions of my site on the web, and how can I get them all to ping to the right place?
Is there a DNS setting somewhere that needs to be changed with my host? Or is this some kind of DNS/routing error?
THANKS
|
| Posted by relichost, 03-12-2008, 02:54 PM | | Hi
If you use some tools like DNSstuff then it should become apparent, if there is an issue with the DNS, it does sounds like one has one setting and the other has the old setting, so they probably aren't getting synced.
Hope that helps.
|
| Posted by Domainitor, 03-12-2008, 03:05 PM | | This sounds very much like you've got a dangling nameserver. Which is to say, you think you've got ns120a and ns120b.genericdns.com set for your domain but, in fact, there are one or more additional nameservers tied to the domain.
Don't set 'em to your old values. That's counterproductive.
But when you do a WHOIS, does it only show the two nameservers that you think it should? Or are there others, too?
|
| Posted by kenfused, 03-12-2008, 03:53 PM | | According to domain tools:
ICANN Registrar: ENOM, INC.
Created: 2002-07-30
Expires: 2008-07-30
Registrar Status: ok
Name Server: NS120A.GENERICDNS.COM (has 2,845 domains)
Name Server: NS120B.GENERICDNS.COM
Whois Server: whois.enom.com
As far as I know only these 2 nameservers...
|
| Posted by UNIXy, 03-12-2008, 04:30 PM | | Try tracing the DNS response. Do a "dig yourdomain.net +trace" from the computer where you're getting the stale IP and post the output here.
GL
|
| Posted by kenfused, 03-12-2008, 04:43 PM | | Ok, thanks I'll have to wait until tomorrow when I'm back at that computer...
Do I do this thru Windows "Run" and "CMD" where I did the ping?
Oh, and are there other WHOIS tools that I can use that might show the other results? (the stale IP)
|
| Posted by UNIXy, 03-12-2008, 05:11 PM | | Download the tool (dig) from here: http://members.shaw.ca/nicholas.fong/dig/
Once installed as in the tutorial, you should be able to run the command from CMD. Post both the stale and correct output here.
|
| Posted by foobic, 03-12-2008, 05:52 PM | | Ah, a Windows binary of dig - that's handy!
kenfused, what you describe is nearly always caused by having the old nameservers set as NS records on your new hosting account. You can check this using dig (downloaded as above) with:
Or go to a dns test site like dnsreport.com or intodns.com and run their report, where you'll see the old nameservers popping up as "stealth nameservers".
If you have access to edit dns records through your control panel you can fix this yourself, but more likely you'll have to ask your host.
|
| Posted by kenfused, 03-12-2008, 06:07 PM | | OK, I ran the report.
INteresting, no stealth DNS, however, should there be 207.210.88.89 and 207.210.88.88
My site is only on the IP ending in .88, not .89, is this a problem?
WHat are the recursive queries?
(sorry so long, this is from intoDNS)
OK, I ran the report
|
| Posted by foobic, 03-12-2008, 06:31 PM | | The .88 and .89 IP addresses aren't a problem - those are your 2 nameservers. Recursive queries aren't a problem for you (although it's a bad setup and might possibly become a problem for other people). No glue - most likely your domain isn't a .com or a .net? If so that's normal. And no stealth nameservers, which is good.
In short, there's nothing there to account for your problem...
|
| Posted by Panopta, 03-12-2008, 07:03 PM | | Have you ever setup a hard-coded IP address for the site in the Windows equivalent of /etc/hosts (can't remember the full path in Windows - search for "hosts" to find it). That might be causing that one machine to see the wrong address because it's bypassing DNS entirely.
|
| Posted by tix3, 03-12-2008, 07:11 PM | | the path is %systemroot%\system32\drivers\etc\hosts
|
| Posted by plumsauce, 03-13-2008, 01:16 AM | | Did you decommission your old name servers?
Or at least get the zone removed from the old name servers?
If not, then you need to do it.
I won't explain why because it involves me bashing a piece of dns software.
|
| Posted by Domainitor, 03-13-2008, 09:53 AM | | If the old name servers are no longer listed as authoritative, why bother? There won't be any queries to them....
I'd like to know why you say that. And what software do you want to not bash? BIND? If so, too late! It's been being bashed for years.... (Did the OP identify the old name servers? How do you know what they're running if not?)
|
|
 Add to Favourites
 Print this Article
|
