feature request for some future distribution: It would be grand if resolv.conf modifications supported an "always-on" set of DNS options in case the stuff provided by the local LAN is fubar or doesn't have zones you want.
in /etc/sysconfig/network one would add something like ALWAYS_ON_DNS=a.b.c.d ALWAYS_SEARCH_DNS=myzone.tld the DHCP client would then write its new resolv.conf, after which nameserver $ALWAYS_ON_DNS would be appended. If no search domain has been specified by the DHCP server, then search $ALWAYS_SEARCH_DNS will also be appended. This is because it's really annoying to sign onto a new LAN and have X apps unable to find themselves because your search line has been overwritten by a braindead DHCP server. Jack On Fri, 2003-02-21 at 09:26, rrowan wrote: > https://qa.mandrakesoft.com/show_bug.cgi?id=1659 > > > > > > ------- Additional Comments From [EMAIL PROTECTED] 2003-02-21 18:26 ------- > It is still valid, although I have no idea if it is really a problem. It causes no >problems here. I originally reported this as a bug for two reasons. One, because it >MAY affect someone with a different setup. Who knows. Two, for consistency. If the >other scripts check for some reason, maybe this should also. > Anyway, someone who knows more about this should at least set this to a lower >priority, or possibly close it if it isn't a problem. > > > > ------- You are receiving this mail because: ------- > You are on the CC list for the bug, or are watching someone who is. > > > > ------- Reminder: ------- > assigned_to: [EMAIL PROTECTED] > status: UNCONFIRMED > creation_date: > description: > /etc/ppp/ip-down seems to be the only script that does not first check either >$PEERDNS or $RESOLV_MODS before editing /etc/resolv.conf. It probably should. -- Jack Coates Monkeynoodle: A Scientific Venture...
