My resolv.confs tend to be written once and then go untouched for months if not years. The problem there is that distributions, be it linux or bsd, lack a prop

My resolv.confs tend to be written once and then go untouched for months if not years. The problem there is that distributions, be it linux or bsd, lack a proper way to distinguish between a "static" resolv.conf and a (always-)generated one. An "easy" fix would be to mandate that if /etc/resolv.conf contains a "dynamic" key then /run/resolve.conf (or /var/run/resolv.conf or whatver) is read as well (or instead). However, tons of stuff tries to parse resolv.conf, so it would be better to have a user-editable /etc/resolv.conf.conf and a /run/dynamic-resolve.conf and dump the result or into /etc/resolv.conf to keep compatible.