Hi, We've closed one of our offices and relocated one of the servers to another site (around 8 weeks ago) I'm based at yet another site. All of our sites are linked by VPN's, each site is a separate domain with trusts setup to the others. The relocated server is called cep4 and used to have the IP address 192.168.0.4, it now has the IP address 132.147.30.4 (which is actually an internal address, I don't know why we dont follow the usual 10.10. or 192.168. conventions, that is outside of my control) At it's site it's address is resolved correctly. From my site it's address is still resolved to 192.168.0.4 unless you use it's FQDN. The addresses of other servers at that site eg. cep2 are resolved correctly. I've checked the forward lookup zone for that domain/site and the server is listed with the correct address. I've transfered the zone from the master, cleared cache, restarted DNS service etc. and it still resolves to the wrong address. anyone got any suggestions ? Cheers

Look for a hosts file? Use tracert for that ip. Does that IP resolve on public routers?

Hi Jefro, There is no hosts file entry, it only has localhost. I've also tried it from several machines. tracrt returns P:\>tracert 132.147.30.4 Tracing route to atglab004.ca.caldera.com [132.147.30.4] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms 132.147.80.10 2 * * * Request timed out. 3 79 ms 74 ms 74 ms atglab004.ca.caldera.com [132.147.30.4] Trace complete. Interestingly tracert for 132.147.30.2 which is a server at the same site that we can access ok just times out. The IP resolves on public routers to a ca.caldera.com server, as do the IP's of most of our servers.