DNS issues? Website not browseable internally

[fordy1765]

Hi,
Our company website used to be hosted on one of our servers (server 2003 DC/DNS/DHCP/IIS6...). I simply pointed the domain at it and added host headers. It is now hosted elsewhere and I amended the A records accordingly with our registrar.
I removed the zone for the .com domain (internally it is .local) and stripped out all host headers. There are still a few subdomains that are pointing at my servers for various hosted web applications. nslookup from all servers (set up the same at 4 sites) gives the right address although reports the name servers (my registrars) as non authoritative.
I can ping from 3 sites but not the 4th. Tracert is slow, as is loading the web pages at these 3 sites, but times out, as does the web page, at the 4th. I have tried changing forwarders to Google 8.8.8.8 and 8.8.4.4 with the same results.
I can ping from the broadband router at each site and it works perfectly externally so I am assuming that the problem is internal.
PLEASE HELP as this is driving me mad.
Cheers
Graeme

 

[ShackDaddy]

How many internal DNS servers do you have? When you ping from the bad site, does the ping show that the IP has been resolved? If so, it's not a DNS issue at all, it's just an IP routing issue. The fact that tracert times out after a few hops also indicates that it's a routing, not resolution issue.

Dave Shackelford
ThirdTier.net