I'll try to explain my situation.

I'm at my home network with a router (192.168.0.1) using iptables and dnsmasq running debian stable
My clients 192.168.0.0/24 are running debian testing.

On my client i have running eth2 (lan-device) which uses the router as dns and a tun0 device wich is a openvpn connection to my work.
I use resolvconf to add the dns and domain of my work to /etc/resolv.conf .

Now when i have the tun0 device not active (vpn is not up) i can ping internally to "router" but when i have the vpn up (tun0) and the dns addes to my /etc/resolv.conf by resolvconf, the it tries to resolv my "router" by the dns of the vpn connection.

When i change the interface-order setting of resolvconf i can manage to ping locally but then the VPN dns isn't working.
Is there any way to get this right using my setup?
so that i can use local dns fine (hostnames) and dns for work fine without having to switch off and on the vpn all the times (very usefull for my imap mail over vpn.)

Thanks,

Sputnikc,

10 years on, I see no reply, and I find myself with exactly this same issue. I wonder if you ever worked it out. I am thinking there must be a resolvconf.conf setup that stipulates what we want here, that .lan always gets resolved on the LAN DNS, that .whatever gets resolved through the VPN defined DNS and that names with no dots depend on the config somehow ....

I can't really follow the man pages so am searching on-line for help and only found this for now. Not unusual to have a problem and only find others with the same problem but no solution ;-).

Regards,

Bernd