Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

We just changed the IP address of our web site, but I don't know how to get my client's mac to look at the new site.

She is seeing the "site has moved" message, but everybody else is just fine. I tried a hard fresh in firefox and flushed the cached in OS X 10.5.8

What do I tell her to do?

When I ping the site it goes to 67.xxx.xxx.xxx When she pings the site is goes to 207.xxx.xxx.xxx

Is this a problem with the ISP? (att in Florida)

Update:

The site resolves properly in Oregon California Colorado

The site resolves to the OLD ip address in Miami, FL

The Florida computer is going to what USED to be her site, but is not a holder page. Everybody else is getting redirected by the old host's DNS to the new host's IP while the nameserver changes at networksolution resolved.

share|improve this question
3  
with the original title i really thought you were trying to redirect mac.com and keep the managers blissfully unaware... –  quack quixote Jan 16 '10 at 0:18
1  
can you determine (via dig or nslookup) where the bad IP is coming from? –  quack quixote Jan 16 '10 at 0:37
    
The IP address is that of the old server. Her computer is resolving incorrectly (or hasn't updated how it resolves) Her ping and tracert are accurate, for the old server. –  MrChrister Jan 16 '10 at 0:59
1  
@MrChrister: yeah, that was obvious. you need to check the DNS servers directly, via the dig or nslookup tools. the bad IP is coming from somewhere; might be the DNS server her computer is configured to use, a DNS server that server is talking to, her computer's cache, etc. the tools i mention allow you to query the servers directly to find out what they know. –  quack quixote Jan 16 '10 at 1:15

3 Answers 3

up vote 5 down vote accepted

The term Client makes me think this person isn't using your network? If you 'just' changed the IP, this is normal, it can take hours for DNS changes to propagate across every DNS server. If the problem persists tomorrow, look for solutions - otherwise, point her towards the IP, not domain, for now.

If it's not the ISP, make sure her /private/etc/hosts file doesn't have any rules that could redirect the URL, and she's not browsing through a proxy server that could potentially be caching DNS entries (many corporate proxies do this to reduce bandwidth load and improve loading times) - also make sure the behaviour doesn't carry on between browsers (some browsers cache DNS more aggressively than others, though this shouldn't be a problem unless something's gone wrong), but if everything is alright, I'm not sure what the issue could be!

share|improve this answer
1  
sorry, phoshi, doesn't look like this'll get you any closer to that Mind Reader badge... –  quack quixote Jan 16 '10 at 0:36
    
@Phoshi - you are right. I was being a prick and you didn't deserve any attitude from me. If you do an edit on your answer and I will remove my down vote. –  MrChrister Jan 16 '10 at 1:00
    
I have updated the question. I was being childish under pressure. I apologize to anybody I have offended. It is not excusable. –  MrChrister Jan 16 '10 at 1:01
1  
It's alright - we all have the right to get a bit snappy under pressure - I'd be a hypocrite if I said otherwise! Updated the answer with a few more things, just in case! :) –  Phoshi Jan 16 '10 at 1:13
1  
note the title indicates boss-lady is on a Mac. not sure where they keep their hosts files... –  quack quixote Jan 16 '10 at 1:17

You can add the HTTP headers:

HTTP/1.1 Moved Permanently
Location: http://www.example.com/

to the header messages. This will redirect all browsers, robots, etc. to the new URL.

share|improve this answer
    
Everybody in the planet has the new URL, just this computer pings to the wrong IP address –  MrChrister Jan 16 '10 at 0:07
    
Ended up doing this, but I have asked a question as to why I needed to. This is just a temp fix until the nameservers update –  MrChrister Jan 16 '10 at 6:26

According to serverfault.com, this is what happened

http://serverfault.com/questions/103281/why-did-this-website-dns-change-fail-in-some-parts-of-the-us

Sure I did the transfer and everything worked as I expected, but the TTL was cached all over the internet, and depending on the path followed from the request to the destination, it might have gotten side tracked. I have to wait for the TTL on the old host DNS server to expire BEFORE everthing is ok again.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.