Summary: | ip-up script shouldn't change /etc/resolv.conf when a dnsd (dnsmasq/pdnsd) is running | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Rolf <mi.rolf> |
Component: | Current packages | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ip-updown.diff |
Description
Michael Rolf
2004-06-24 03:02:39 UTC
Good idea Michael - feel free to submit a patch. Created attachment 39729 [details, diff]
ip-updown.diff
Patch to the ip-up and ip-down scripts for ppp 2.4.2.
This is basically what I use so as to not replace the /etc/resolv.conf when
using a local nameserver (dnsmasq). Also includes a check for
/etc/ppp/resolv.conf which most other distributions have.
quote from pppd man page: usepeerdns Ask the peer for up to 2 DNS server addresses. The addresses supplied by the peer (if any) are passed to the /etc/ppp/ip-up script in the environment variables DNS1 and DNS2, and the environment variable USEPEERDNS will be set to 1. In addition, pppd will create an /etc/ppp/resolv.conf file containing one or two nameserver lines with the address(es) supplied by the peer. I don't see why we should refuse to use peer DNS when someone has 127.0.0.1 as nameserver in its original resolv.conf. If user decided to use it, why denying its right to do so? |