Good Morning everyone  We have a strange problem occurring in one of our customers. Historically, this was a domain: [customer.com] so the web site zone had local DNS for local users within the domain. (I personally think that was a mistake, but this is the way it was) All modification had therefore to be entered statically in the DNS for internal domain customers to access the web site. We upgraded, changed the servers and deleted this domain then re-created a new domain: [ho.customer.local] With a nice windows SBS 2003 R2 IBM server, with ISA 2004 FW installed. Then we downgraded all the PC form the old domain [customer.com] and installed then on the new domain [ho.customer.local] After finishing all the setup, we are facing a strange problem: All computers (including the server) can access all web site, Excepted customer.com (the old Domain) we have tried all setting, and we are running out of idea, WHY can’t we access the customer.com web site? Help would be highly appreciated  Thanks in advance  Mat.

Just to clarify a few things, a dot local domain is not routable to the outside but a doc com domain is. People make the mistake of calling their local domain dot com. The question is: Is customer.com a FQDN and where is it being hosted? If it's not a FQDN, then the DNS won't be able to find it and it shouldn't be a dot com.

Yes, the local domain is not routable, he has the same prefix that the .com domain for convenience reasons. The domain we cannot access is a public hosted domain with a .com extension. I forgot to mention that I have a dns resolution on customer.com and that I can also ping it. the tracert is fine as well. the only thing is that I cannot open it from Any Web browser...

Point your name server entries to those of your ISP and not your local server. The DNS records from the previous setup may not have been updated when you made the change.

Well actually they did since I have a proper DNS resolution and I can ping the [ .com] web site from the local AD domain. The local DNS only resolves AD on the local side. then there is a set of forwarders for the [ .com ] web site resolution.

Instead of using ping, use pathping and follow the hops.

O)k, found the problem, the server public IP ended up black listed, this is why I could not access using port 80. thank you all for the Help :) Mat.