On Sunday, July 26, 2020 7:06:48 PM MST Michael Catanzaro wrote:
On Sun, Jul 26, 2020 at 6:15 pm, John M. Harris Jr johnmh@splentity.com wrote:
Please do not disable reading from /etc/resolv.conf. If you do so, please limit that to the Spins that it won't affect people on, such as Workstation, if you believe people there don't set their own DNS servers.
Except:
- /etc/resolv.conf is broken by design, as you would know if you read
the section on split DNS that you just quoted
/etc/resolv.conf is not broken. It's the standard way of defining DNS servers for systems, and has worked for well over a decade.
- There's no value in reading from /etc/resolv.conf unless you have
written something custom to it
The value is actually getting DNS lookup to work on users' systems. Unless they've only used NetworkManager, and never touched /etc/resolv.conf, their system *will not be able to resolve hostnames after this forced removal*. There's a clean way to prevent that. Do not remove the file upon update.
- /etc/resolv.conf is managed by NetworkManager in Fedora, so you
cannot safely write to it anyway in our default configuration
/etc/resolv.conf is managed by NetworkManager, but it only gets updated if you use NetworkManager to manage DNS.
Fact is that unless you have done custom work to allow manual modifications to /etc/resolv.conf, you're not going to notice this change at all.
This is literally removing the file upon upgrade. That wasn't there originally, and it's a horrible addition. See your original response when I brought up this concern..
And if you have, then surely you'll be able to figure out the very, very simple steps to get back to the original behavior. In fact, it should actually be *easier* than before to get traditional behavior. Remove the symlink. Create your own /etc/resolv.conf. Hey presto! systemd will read it....
Is that what will actually happen, or will systemd still continue to ignore it? That's not made clear, because we've decided to go with something other than what Lennart calls "mode 1".