Hi Phil, On Thu, May 17, 2007 at 02:50:53PM +0200, Phil Sutter wrote: > * all routers (as our target devices potentially all are) will either > fall into the first category defined here, or will even be part of the > dns system of the subnet they provide. The latter is very likely, as > private LANs seldomly make use of different machines for routing and > dns.
What if there are two dynamic links that connect the machine to the internet (ppp, vpnc, umts, lan, ...)? If the order of ifup is not the inverse one of ifdown, the restoring of nameservers will fail if a link goes down. So removing exactly the nameservers that were added by the link will solve the problem if there are different nameservers on each link. > * how to handle dhcp clients? None of them supports intelligent editing > of resolv.conf. What about using a simple shell script that is given the nameservers like in vpnc on connect? On ifdown, one could use stored values from a tempfile. > * Who cares about the precedence of different nameserver entries? Having > some entries with dead nameservers before any valid one actually > causes big delays when resolving names. So it is important, to remove the "correct" nameserver entries from resolv.conf if a dynamic link changes state. In case there is a static link, that is always up, there is no need for more than the nameservers given by the static link - here i agree with you. _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
