VPN Routing

[Guest]

I have a network that was setup a very long time ago that uses <domain>.com
for the Active Directory domain name. This domain is so old, they actually
had public addresses back then. Now of course I have them on a private net,
but the domain is still the .com, and their web sites are all hosted
off-site. This causes some nasty DNS problems. I can control these using
DNS internally, but now they want VPN. Specifically Exchange via VPN, but
they also want access to other servers.

Anybody know how to force the VPN clients to resolve to the internal domain?
Right now, email.<domain>.com resolves to the DNS that is SOA for their
public domain.

 

[Kurt]

Here's an undocumented (and really, wrong) configuration that works.

List the Internal DNS server as the preferred and a public DNS server as the
alternate. When the VPN is not up, no connection to the preferred server can
be made, so clients will fall back to the alternate. When the VPN is
connected, the whole routing table gets updated, and once again, the clients
will attampt to contact the primary DNS server, which is now reachable. This
is a little flakey, but it works.

....kurt