Hi all,
I was reading the manual page of resolv.conf(5) today and realized that
paragraph on resolv.conf.tail has disappeared since the upgrade to 7.0,
so I assume that resolv.conf.tail has been deprecated in response to
resolvd being enabled by default.
Previously, my backup strategy was to back up the customized system
configuration files, which involves backing up resolv.conf.tail, but
not resolv.conf. With the new behaviour in 7.0, it appears that my best
shot is to back up resolv.conf, which constantly gets edited by
resolvd(8). This seems less than ideal.
I gave it some thoughts, and came up with an alternative solution to
handling resolv.conf:
- If resolvd is enabled, then resolv.conf is overidden entirely by
resolvd, no more blending of user-edited and auto-configured
information is involved. A new resolvd.conf needs to be introduced to
instruct resolvd to add static defaults and stuff;
- If resolvd is not enabled, then the contents of resolv.conf.tail gets
copied to resolv.conf at system start.
To me it seems that this is cleaner than the current solution to
resolv.conf in that static and dynamic configurations is clearly
separated instead of being blended into a one file.
What are your thought on this? Thanks!
