phbrowne — 2011-08-02T11:34:43-04:00 — #1
Let me start by saying that I am not a networking expert...
I have a client who cannot see their new web site. Trying to view the site from anywhere on their network sends them back to their old IP address where they see a confirmation page "you are viewing the old site."
The client of course was convinced it was something on my end until I told him to take out his phone and try viewing the new site - which he could no problem. Any other computer sitting outside their network can view the site fine.
This leads me to believe that the DNS has propagated but the client still has some internal settings somewhere that are directing them to the old IP.
Their set up: 22 sites networked together (they have tried from several sites -all the same which leads me to believe that it is a top-level issue rather than a machine or site issue). Firewall software which they have set to strict filtering standards (it is a school). Websense Triton 2010. They have also specifically unblocked all four IP addresses (two at the old host and two at the new host).
Networking software - I am still trying to find out but they have a mix of old and new systems. (call in to the admin to get this info).
The computers are a mix of mostly WinXP with a few Win7 and Macs.
When they type in domainname.com they get redirected back to the old IP. When they type in www.domainname.com they get a firewall warning message. This is how they have had it set up for years - back when it actually mattered whether you had www. in front of your domain or not. This leads me to believe that it is not the firewall software but rather some company internal network setting.
I asked them to clear their HOSTS file on a couple of computers and check that, still the same. Again, leads me back to top-level network problem.
They tell me that they have set up the firewall to configure all the sites as friendly. There has got to be something else at play here.
system — 2011-08-02T14:35:13-04:00 — #2
Delete all the cookies, catche, history of the browser and restart the computer, then try
eastcoast — 2011-08-02T19:54:28-04:00 — #3
Get them to find out whether their network client PCs are getting their DNS from the network server or the ISP. If it's the network server then flush its DNS cache (administrative tools-> DNS snap-in). If the client PCs are getting DNS directly from the ISP then try changing one to e.g google on 18.104.22.168 and 22.214.171.124
chriswiegman — 2011-08-03T14:46:42-04:00 — #4
Sounds like a DNS cache issue. I've seen poorly configured DNS servers cache lookups for weeks beyond the record's expiration. Try setting them up with something like OpenDNS | DNS-Based Web Security and see if that helps.
ffcus — 2011-08-03T16:49:06-04:00 — #5
I have a client that has an internal DNS at their organization. We had the same issue. Their IT dept. had to go an and update the record for the domain name to point to the correct IP. Until they did that, the domain went to the old site internally but the new site for everybody else.
Do they have an IT dept. that handles their DNS?