Hello,
As far as i can see (i may be wrong) this setting defines how the DNS servers
are contacted. For example on whether to use DNSSEC or not.
But it does not define - based on the domain or subnet part (for reverse
lookup) - which DNS server is to be queried.
Kind regards
Petric
> -Or
have a look at NRPT (which is "name resolution policy table")
https://technet.microsoft.com/ru-ru/library/ee649207%28v=ws.10%29.aspx
however, openvpn doesn't yet support that
2015-01-20 15:56 GMT+05:00 Frank, Petric (Petric)
:
> Hello,
>
> this is not exactly a OpenVPN problem.
>
> I connect via
: *Re: [Openvpn-users] DNS from network behind VPN
*From: * Keijser
*To: *Pavel Bychikhin
*Cc: *openvpn-users@lists.sourceforge.net
*Date: *21.01.2015 23:49
Hi Pavel, *,
On 20/01/15 13:54, Pavel Bychikhin wrote:
I send my clients a `domain-search' option via DHCP. First domain
from that lis
Hi Pavel, *,
On 20/01/15 13:54, Pavel Bychikhin wrote:
I send my clients a `domain-search' option via DHCP. First domain from
that list is used by Windows as a `Connection-specific DNS Suffix'.
This does the trick. Windows uses this connection to query for names
within domain of a `Connection-
I send my clients a `domain-search' option via DHCP. First domain from
that list is used by Windows as a `Connection-specific DNS Suffix'. This
does the trick. Windows uses this connection to query for names within
domain of a `Connection-specific DNS Suffix' even if a PC is in Active
Directory
I'm pretty sure it's not possible to do that from a windows perspective,
however the workaround that I've used (that has some advantages of its own)
is to run the bind dns server locally on my windows client machine,
configured as a resolver for localhost only, and configured with forward
zones for
