"Eric" <(E-Mail Removed)> wrote in news:ImwYf.72202$9I5.58146
@tornado.ohiordc.rr.com:
>
> "Scott Moseman" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
>> The "DNS and Bind" book make cover getting your DNS server setup, but I
>> doubt it is going to help you too much getting the VPN setup. Do you
>> already have a VPN setup? If not, that is going to be much more
>> complex than setting up a simple DNS server.
>>
>> Thanks,
>> Scott
>
> Not yet. I was going to mess with OpenVPN. http://openvpn.net/
>
> It runs on multiple platforms and should be do-able. Most of the
> "client-side" computers are going to have dynamic IP's, hence wanting to
> setup DNS server (on a static IP, of course) rather than deal with any of
> the dynamic IP services (i.e., dyndns.org).
>
> Thanks...
>
>
It's simple. Just make sure that the subnets that your private DNS servers
sit on are included in the 'push route' or routes configured on your OpenVPN
server. Then make sure that your private DNS servers' IP addresses also get
pushed to the client when the OpenVPN client connects (that is one of the
'push dhcp-option' settings). If the client PC is running Windows then you
need to make sure that the virtual adapter used by the OpenVPN client has the
highest priority (this should normally be the case anyway unless you added
the physical adapter after the OpenVPN client software was installed. (You
can change the priority it under the adapter properties advanced settings).
For a Linux client, I believe the resolver.conf will get replaced by the
OpenVPN settings pushed from the server (should get put back as it was when
the OpenVPN connection closes). Of course your private DNS servers must be
able to deal with public internet name lookups otherwise the remote client
will only be able to resolve private names while the OpenVPN connection is
up.
Klazmon