If I understand correctly, the problem arises because the road staff's TCP/IP connection is receiving the DNS server info automatically from whatever connection they are using. If you set up the clients to use a preferred DNS server as something like OpenDNS, available from anywhere, and your secondary DNS server as the internal IP address of your local LAN's DNS server, you should get the effect you want. When your users are on the road, they will use OpenDNS. When they are back in the office, the requests for local names will go to OpenDNS and fail, and then be directed to the local DNS server.
Didn't Gopher fade because the University of Minnesota wanted licensing fees for Gopher servers and you could get the CERN and NCSA HTTP servers for free?
Slashdot Mirror
Any movie would have to work hard to be funnier than Eddie Murphy as "Eddie Asteroids" with Joe Piscopo on Saturday Night Live.
If I understand correctly, the problem arises because the road staff's TCP/IP connection is receiving the DNS server info automatically from whatever connection they are using. If you set up the clients to use a preferred DNS server as something like OpenDNS, available from anywhere, and your secondary DNS server as the internal IP address of your local LAN's DNS server, you should get the effect you want. When your users are on the road, they will use OpenDNS. When they are back in the office, the requests for local names will go to OpenDNS and fail, and then be directed to the local DNS server.
Changing the social and political structure of the world just might take longer than six years.
Didn't Gopher fade because the University of Minnesota wanted licensing fees for Gopher servers and you could get the CERN and NCSA HTTP servers for free?