Bug 21649 - USEPEERDNS=YES crept back into initscripits
Summary: USEPEERDNS=YES crept back into initscripits
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-03 15:48 UTC by Henri Schlereth
Modified: 2014-03-17 02:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-04 02:04:53 UTC
Embargoed:


Attachments (Terms of Use)

Description Henri Schlereth 2000-12-03 15:48:39 UTC
USEPEERDNS is again set to yes which means that ifup-ppp rewrites resolve.conf and eliminates the
nameserver settings and replaces them with the ISP's DNS. This effectively kills internal DNS resolves
when using RFC1918 IP's for example.

Comment 1 Bill Nottingham 2000-12-04 00:26:35 UTC
Yes. Is there a reason you can't unset it in your case?

Comment 2 Henri Schlereth 2000-12-04 02:04:50 UTC
Of course I set it back, but can you give me any good reason why I had to do that? I dont consider it a feature if it over writes my
resolve.conf with DNS entries that I dont need/use. The ifup-ppp should be an rpmnew. I was upgrading a server that provides services for
six internal machines not a  standalone dial-up workstation. My DNS servers knows how to talk to the ISP DNS servers without
them being in resolv.conf.  This has never been an endearing feature since it was instituted. It may be wonderfull and helpful to
the helpless but not to the rest of us.


Comment 3 Bill Nottingham 2000-12-04 02:08:32 UTC
ifup-ppp should not be made into an rpmnew file; it's not a config file.
In fact, it probably shouldn't even be marked %config.

To turn off support for this, set PEERDNS=no in whatever ifcfg-<interface>
file you're using.



Note You need to log in before you can comment on or make changes to this bug.