Description of problem:
sortlist entries added to /etc/resolv.conf get clobbered by the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.edit /etc/sysconfig/networking/profiles/default/resolv.conf to contain
a sortlist entry
2.start up the redhat-config-nework GUI and go to the DNS page
sortlist entries in resolv.conf get trashed
GUI should ignore but preserve entries it doesn't understand
Occasionally something re-generates /etc/resolv.conf from preferences buried
somewhere in /etc/sysconfig, especially when using PPP as the primary network
interface. So adding sortlist entires to /etc/resolv.conf is out of the
question. It is interesting that such entries in
/etc/sysconfig/networking/profiles/default/resolv.conf also get trashed by the GUI.
could it be, that pppd changes your /etc/resolv.conf?
I think pppd moves /etc/resolv.conf to /etc/resolv.conf.bak ...
If you start r-c-n it takes /etc/resolv.conf as the actual system state and
copies it to the default profile
Yes, quite possible. Something is creating /etc/resolv.conf.save at the start
of the PPP session, there is nothing in the pppd manpage about this, don't have
the soruce rpm handy right now to grep for this behavior. Apparently the
overwrite of /etc/resolv.conf occurs only if /etc/resolv.conf differs from what
pppd wants it to be. A new /etc/resolv.conf.save is always created at session
start, but /etc/resolv.conf is only overwritten if it has custom entries.
I'll have to check the pppd source to see what is causing this. Sortlist
probably isn't common in most people's setups, but we have enough multi-homed
machines with addresses not routed on the normal part of the campus network,
that stuff like kerberos starts failing if sortlist isn't in resolv.conf.