From: Joseph L. C. <JC...@ac...> - 2009-08-03 13:49:33
|
>If I didn't it clearly before, I'll say it now. I'm not the only one. I've had >this problem at every single client site where I have used open VPN in the past >eight years. The vast majority of time it didn't show up because end-users were >just people working from their home network and therefore the office DNS could >provide all of their Internet DNS related needs. I'm finding more and more >technically astute people having local networks at home with miniature DNS >setups. I find out about it when they call me saying "when open VPN is running, >why can't I access any of my machines at home?" I'm also following this thread with interest as I lurk before my first setup with OpenVPN. In my PIX that I am replacing, it's called Split-DNS and is obviously intrinsic to the function of the VPN. All of my needs revolve around remote users getting RDP access to their wkst's as we don't allow file sharing through the vpn and most of the files they open are prohibitively large files anyway. My users are trained to connect to the FQDN of their dynamically assigned wkst's which makes my administrative job easy. The cisco split-dns has the search domain setup that *.example.com goes across the tunnel. Simple... I hope you figure this out, if so please post back! jlc |