Site on new host not visible to client.

[iany]

Having just completed a new site for a client, the existing domain then had nameservers changed to new host and hence new site. Within a couple of hours, new site was working in its new home. Unfortunately the client could not access emails as his system could not "see" the new site. Clearing the cache - or even using different browsers made no difference. As the .co.uk is the default domain with the .com mapped on to it, we tried the .com version - which worked fine on their system. In order to access the email we then had to change the mailservers to .com - all quite bizarre.

We even had their IT contractors in on the problem who could not solve the issue either.
To add insult to injury, I had my computer linked to a mobile wireless and, therfore, separate from their sysem, which had everythin working as it should.

I have not come across this before. Any one have any ideas? Or is it just a case of wait until DNS has finally made all changes?

Look forward to your thoughts.

Best

Ian

[speed]

Sounds like the nameservers being used by the client computer haven't updated yet, wait 48 hours and see if it then works.

You could also try swapping the clients computer to use OpenDNS (http://www.opendns.com/) or Google Public DNS (http://code.google.com/speed/public-dns/), if one of those works then the fault lies at the nameservers currently used by the client.

You can also check the PC that isn't working for a misbehaving DNS cache, many moons ago I had this issue with the cache in and old version of Outpost Firewall.

To give any more information you would need the domain name in question and the IPs of the machines the client is using to resolve domain name queries, with that you can start looking for the issue if there is one.

[iany]

Speed,

Thanks for quick response.
I should have mentioned that all computers on site are acting the same. I wondered if it were a problem with their network server. We pinged the site and it brought up old IP address.

Very strange

Ian

[speed]

Then all that's happened is that the nameservers they are all using to lookup the IP for the domain haven't updated yet, either you're not waiting long enough or they are ignoring the settings on the domain and using their own values for time to cache the information.

If you have a server on the LAN which is responsible for resolving DNS queries then see if that's stuck, if you are using your ISP then try one of the other 2 providers that I gave you, obviously you need to make sure the ISP updates eventually.

If it's been less than 48 hours since you change the nameservers on the domain then I wouldn't worry about it.

[timmathews.com]

iany,
Was this resolved? What was the issue?

[aliceandmosee056]

I would suggest that you should wait for some time may be 2 to 3 days and do check your clients computer for the cache memory.

[iany]

Sorry folks,

I thought I had updated this.
We reckon it was the ISP that had not updated.
To answer some of the thoughts.
I and several other people outwith the organisation could see new site on the .co.uk domain so clearly could not have been a nameserver issue.

The cache was cleared on the system (that was first thing we looked at).

It took a few days for the btinternet to update (3 days) and all was ok after that.

Thanks all for your thoughts.

Cheers

Ian