<![CDATA[OpenVPN: Windows clients use option dns server as their default dns]]>Hi,

I got a problem with windows clients connecting via OpenVPN.
As long as I provide them with pfsense's dns server (forwarder), they use it as their default dns server. It doesn't matter whether I set a default domain or not.

The reason I don't want this to happen is that I'm overriding the hostname/address of a particular host in the lan in the dns forwarder. This should only take effect for local clients but not remote clients.

Is there any way I can solve this remotely via some switches in the openvpn server config?

Thank you very much!

]]>https://forum.netgate.com/topic/25948/openvpn-windows-clients-use-option-dns-server-as-their-default-dnsRSS for NodeWed, 12 Aug 2026 12:10:06 GMTFri, 20 Aug 2010 14:05:35 GMT60<![CDATA[Reply to OpenVPN: Windows clients use option dns server as their default dns on Sun, 22 Aug 2010 19:46:51 GMT]]>tinydns doesn't allow that AFAIK, believe you'll need BIND.

]]>https://forum.netgate.com/post/244053https://forum.netgate.com/post/244053Sun, 22 Aug 2010 19:46:51 GMT<![CDATA[Reply to OpenVPN: Windows clients use option dns server as their default dns on Sat, 21 Aug 2010 12:38:18 GMT]]>Thank you!

So I have to set up bind somewhere, or does tinydns allow different settings per network too?

]]>https://forum.netgate.com/post/243946https://forum.netgate.com/post/243946Sat, 21 Aug 2010 12:38:18 GMT<![CDATA[Reply to OpenVPN: Windows clients use option dns server as their default dns on Fri, 20 Aug 2010 16:32:12 GMT]]>That's how it's supposed to work. Default domain has nothing to do with that. OpenVPN can't control that. That's a Windows question (you can muck with the binding order but it gets to be a real PITA with any type of VPN on Windows).

]]>https://forum.netgate.com/post/243839https://forum.netgate.com/post/243839Fri, 20 Aug 2010 16:32:12 GMT