Yes, this is still a minor issue (years later!) When a new PPP link starts up and USEPEERDNS is set, the script /etc/ppp /ip-up.d/0000usepeerdns replaces all of the nameservers in /etc/resolv.conf.
If you're accessing a PPTP VPN with a private DNS server, name resolution is broken as soon as the PPP link comes up. You can only browse to domains that the private DNS server knows about. My (admittedly simplistic) patch causes the script to *add* the VPN's nameservers to /etc/resolv.conf. The thing is, /etc/ppp/ip-up.d/0dns-up seems to do the same thing in a much smarter way (plus it's aware of the resolvconf package). I'm not sure why the two scripts exist; it seems that 0000usepeerdns is redundant. -- ip-up.d/0000usepeerdns shouldn't clobber /etc/resolv.conf (patch attached) https://bugs.launchpad.net/bugs/38917 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
