AD server within another network - DNS issues

Posted by Harry Muscle on Server Fault See other posts from Server Fault or by Harry Muscle
Published on 2012-11-09T04:28:22Z Indexed on 2012/11/09 5:05 UTC
Read the original article Hit count: 458

Filed under:
|
|
|

Here's a quick summary of the environment I support: we have a domain (domain A) that has about 20 client computers. The domain server for this domain and all the clients sit within the network infrastructure of a larger domain (domain B). All the computers get their network settings via DHCP from domain B's servers. I have no control and am unable to make changes to anything to do with domain B.

The problem I have is that currently in order for my domain's (domain A) clients to be able to resolve the domain server and the shares on it they have their DNS server IP address set to domain A's domain server (via the default GPO). Unfortunately when a laptop (windows and mac) gets taken home, they are still looking for the domain server as their DNS server and obviously can't access the internet correctly outside of our environment. Ideally I need a solution where the machines use domain A's domain server as their DNS when inside the office and use what ever DNS server DHCP gives them when they are outside the office. However, since I have no control over the office DHCP server, I'm not sure how this can be accomplished.

Any help and advice that anyone can offer is highly appreciated.

Thanks, Harry

P.S. The solution I'm trying to find needs to require no involvement from the user.

© Server Fault or respective owner

Related posts about dns

Related posts about active-directory