I have a network in NY where I'm trying to migrate their MS Exchange Server to Rackspace at the DFW Datacenter in TX. The NY network, seemingly randomly, developed a strange DNS issue. The NY office AD domain is foo.com. www.foo.com, shop.foo.com, etc are hosted outside the NY office and are working properly for the outside world. Inside the office all subdomains are not accessible by a browser.
The DNS records to forward the requests are properly installed in MS DNS on the primary server within the NY office. If I NSLOOKUP, it reports the correct outside IP's for www., shop., etc.
I've taken down their ISA Firewall temporarily and still not working. I've taken down their Barracuda Spam Firewall and still not working.
And the weird twist is the browser doesn't immediately report that it can't find the site (www., shop., etc). It will attempt to load the page for about 3 minutes, sometimes will partially load and then fails.
Suggestions? Ideas? I need to fix this issue before I change the DNS for the Exchange Server, or the employees in the NY office won't be able to access mail.foo.com tomorrow morning.
mobile.foo.com seems to work, but shop.foo.com still does not, and they are on the same server outside the office.
It seems the problem is only affecting HTTP.
If I access shop.foo.com on an alternate port (say telnet to shop.foo.com 21) it properly brings up FTP in the cmd prompt.
Upon further review, it looks like it's only www.foo.com that is malfunctioning within the office. the other websites (shop., etc) are using resources from the www.foo.com server and are causing the page time-outs and partial loads.
NSLOOKUP does continue to work properly for www. though. Ideas? Thoughts?