On 10/01/2021 11:04, Tim via users wrote:
Ed Greshko:
When I tested reverting to the previous behavior I simply started
with an empty /etc/resolv.conf.
No symlink. No selinux troubles. Everything just worked.
Sam Varshavchik:
Well, then how do the apps that need to talk to the DNS server find
it? Maybe something in the glibc resolver knows to look in the
alternate locations if /etc/resolv.conf is empty.
Didn't he then go on to say that it was populated? (Letting the system
create that configuration file.) Surely his subsequent tests were
after that stage.
To be specific, I created an empty file by "touch"ing it. Then, on rebott,
since systemd-resolved is
masked NM will populate the file as it always has. In other words, the
previous method of doing
name resolution is in effect/restored.
But there are apps that read /etc/resolv.conf themselves (Firefox
without a proxy?). They'll be hosed now.
Surely apps that only look at that file once are always going to have
failures. The file changes, things need to make allowances for that.
I've no knowledge of firefox reading /etc/resolv.conf directly. As a matter of
fact, I don't
know of any reason firefox or any other app would do that.
Now, since the previous behavior is restored they wouldn't be any less "hosed"
than they
were in F31.
---
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
