[Dnsmasq-discuss] NXDOMAIN problems with open VPN

Eric S. Johansson esj at harvee.org
Sat Apr 18 23:35:47 BST 2009


 this has happened to me with three separate sites so I really need to fix
something.  When I connect to a remote site with open VPN, it rewrites
resolv.conf so that it includes a remote DNS server first and then the local
name server.  When I query for a remote name, everything works fine.  But when I
query for a local name, I get NXDOMAIN.  as I see it, my solutions are fairly
limited.

Is there anything I can do to change the NXDOMAIN response in the remote dnsmasq
instances?

would it make sense to run a local dnsmasq and filter out the erroneous NXDOMAIN
references from the  name servers pointed to by resolv.conf?

I think this is an important problem because it's going to occur any time you
use open VPN and have both local and remote DNS servers.

Thanks for any help


---eric

 PS fwiw, I'm already halfway to running dnsmasq locally because of vmware's
whacked DNS and DHCP setup.



More information about the Dnsmasq-discuss mailing list