From: Joseph L. C. <JC...@ac...> - 2009-08-03 15:32:03
|
>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. I also am pretty sure that the Cisco client did something specific wrt to the dns config that wasn't just as trivial as adding a secondary nameserver: http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/htspldns.html Thanks for the info! jlc |