When connecting to a vpn, the nameserver entry from that vpn connection is added after the one I normally use in resolv.conf. VPNs using both vpnc and pptp both behave the same. Reproducible: Always Steps to Reproduce: my relevent configuration from /etc/conf.d/net config_eth0=( "10.0.0.10 netmask 255.255.255.0 broadcast 10.0.0.255" ) routes_eth0=( "default via 10.0.0.1" ) dns_domain_eth0="xxx.org" dns_servers_eth0="10.0.0.1" which results in the following resolv.conf # Generated by resolvconf search xxx.org nameserver 10.0.0.1 Using openresolv-2.0, I start my pptp connection and correctly get the following my resolv.conf # Generated by resolvconf search xxx.org yyy.com nameserver 10.0.10.10 nameserver 10.0.0.1 using openresolv-2.0.1 I get # Generated by resolvconf search xxx.org yyy.com nameserver 10.0.0.1 nameserver 10.0.10.10 which won't resolve any names on the vpn connection.
Updated to net-dns/openresolv-3.0 today, problem still exists.
You neglected to state baselayout or openrc version. Anyway, could you post the output of the following please? ls -l /var/run/resolvconf/metrics
Created attachment 185393 [details, diff] Work properly for resolv.confs without metrics I think this is the issue you're having. With the new metric support we added in 2.0 everything got a metric. We then fixed metric to actually work in 2.0.1. However, this also meant that the dynamic ordering based in interface name stopped working. This patch only works like so now dynamic order metric order everything else You will have to restart all your interfaces for this to work though.
(In reply to comment #2) > You neglected to state baselayout or openrc version. > Anyway, could you post the output of the following please? > > ls -l /var/run/resolvconf/metrics sys-apps/openrc-0.4.3-r1 sys-apps/baselayout-2.0.0 ls -l /var/run/resolvconf/metrics total 16 -rw-r--r-- 1 root root 2 Mar 15 11:06 0000000 bond0 -rw-r--r-- 1 root root 2 Jan 7 20:17 0000000 eth2 -rw-r--r-- 1 root root 2 Mar 15 11:06 0000000 lo -rw------- 1 root root 2 Mar 18 06:35 0000000 ppp0 I have no eth2, bond0 is eth0 & eth1 bonded, ppp0 is one of my vpn connections (pptp), the other is tun0 (vpnc) which isn't listed.
(In reply to comment #4) > ls -l /var/run/resolvconf/metrics > total 16 > -rw-r--r-- 1 root root 2 Mar 15 11:06 0000000 bond0 > -rw-r--r-- 1 root root 2 Jan 7 20:17 0000000 eth2 > -rw-r--r-- 1 root root 2 Mar 15 11:06 0000000 lo > -rw------- 1 root root 2 Mar 18 06:35 0000000 ppp0 Yeah, the above patch should fix that. > I have no eth2, bond0 is eth0 & eth1 bonded, ppp0 is one of my vpn connections > (pptp), the other is tun0 (vpnc) which isn't listed. eth2 must have existed at some point though. /var/run is deleted when the system reboots, or goes from single user to multiuser. So it's been up a long time? Anyway, you can manually delete the instance resolvconf -d eth2
(In reply to comment #3) That patch fixes the problem, thanks.
This is fixed in openresolv-3.1.1 which is now in portage.
(In reply to comment #7) > This is fixed in openresolv-3.1.1 which is now in portage. You said it. Closing.
