Ok, this is a tricky one: We have a client that has an active directory dns name the same as their internet DNS name. This would be fine except that their web site is hosted externally. So when clients that have their primary DNS pointing to the internal server (as required by active directory) try to access the external web site, active directory thinks it's internal and can't find it. No problem, put in a zone for the internal DNS. That works fine. Now when they try to access active directory sees that it has it and points it to the external site as specified in the dns. The problem is that their web site has thousands of pages and 5% of the links dropped the some reason. So when internal users try to go to those pages, active directory takes the request and can't find the page internally. Changing the pages would be the best idea but this is a satellite office of a 50,000 person company and the corporate office doesn't want to listen. Isn't there a way to make active directory forward dns requests for the local domain externally so they will resolve? I have forwards set in DNS to an external DNS server.