|
From: Les M. <les...@gm...> - 2009-08-03 16:21:37
|
Joseph L. Casale wrote: >> However this depends on the remote DNS server having access to the >> tunnel which often won't be the case since it is likely to be embedded >> in a NAT router or in a DMZ subnet and not running the tunnel. But, I >> don't think there is a good solution where the VPN connection is not >> permanent and you need to alternate access between (say) a public web >> service without VPN and private names in the same domain when the VPN is >> up. > > In my case the AD dns name is private, example.local where the companies > external dns name is example.com. So the clients local dns being provided > by either a small router/isp or like my home, a BIND dns server will never > answer queries to the invalid domain example.local. Windows is sort-of a special case anyway since it has its own concept of names besides DNS. You might make most things work for windows applications by setting a a WINS server address on one side of the VPN and DNS on the other. For an unqualified hostname, Windows will try both netbios (through WINS if available, broadcast if not) and DNS with the default domain(s) appended. -- Les Mikesell les...@gm... |