Comment 12 for bug 923685
Revision history for this message
| Thomas Hood (jdthood) wrote Re: New resolver package overwrites manually created resolv.conf on server | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> Not sure I understand the difference here.
interfaces(5):
Lines beginning with the word "auto" are used to identify
the physical interfaces to be brought up when ifup is run
with the -a option.
[...]
Stanzas defining logical interfaces start with a line
consisting of the word "iface" followed by the name of
the logical interface.
Read the passages on mapping.
> [...]
> Would that break the system?
Appending the original file to the end of resolv.conf can't have terribly deleterious effects. (<Knock wood>) The worst that can happen is that the original file contains obsolete "domain" or "search" lines which override a new valid "search" line. (Only the last one of these counts.) The original file may also list obsolete nameserver addresses but so long as new valid dynamic ones are listed earlier this doesn't make any difference. (Only the first functional address counts.) And listing an obsolete nameserver address only has the effect of delaying the name service failure condition by a few seconds. These issues are minor compared with the problem of resolv.conf *lacking* nameserver addresses that *are* in the original file. That's what will bring the pitchfork-armed admins to our doors.
--
Thomas