Comment 6 for bug 923685
Revision history for this message
| Stefan Bader (smb) wrote Re: New resolver package overwrites manually created resolv.conf on server | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thinking about the debconf message: I think this would be ok for me as sort of occasionally affected. And maybe it would be ok as it would warn any admin to action before a upgrade on a server farm. Or they go mental (and if we are unlucky on us).
So anything automatic might be better. Writing down my thinking (which I admit is quite hard to formulate as a nice script without too many dependencies). If I understand correctly things are bad if
1. there is no active/auto interface in interfaces that uses dhcp and
2. there is no active/auto interface in interfaces with dns-nameservers and
3. there are nameservers defined in resolv.conf
In that case the servers and search need to go somewhere into interfaces and the somewhere is the problem. I wonder whether it would be ok to just pick the interfacce related to the default route...