I do not believe that this is just about lack of fallback and the silent fail.
Although that is probably true, it is also about the "silent" change from nss to
systemd-resolved and THEN the silent change to zero default fallback.
There was a series of silent changes that brought this failure to light.
Not only do I not see the need for a change to a new name service client, the
lack of information about the changeover to users outside this list is a
terrible example for its lack of communication. Although I try to read the
release notes I sometimes seem to miss things or fail to read them altogether.
I am not sure I know how that bit can be fixed but I think it is an organic part
of this failure. Perhaps such deep and basic changes should be mentioned in the
release announcements along with a BOLO for related failures.
Do not misunderstand me. I really like systemd overall. Perhaps you have seen my
series of articles about various systemd tools at Opensource.com. But this bit
does seem a little extreme. I think I have an idea for a new article. "The
layers of Linux." ;-)
Anyway, my personal approach to this is a return to nss by disabling
systemd-resolved until the problem is well and truly fixed. And my name
resolution is now working exactly as it should.
My remaining question is, where can I find a complete description of
systemd-resolved and what its design goals are?
Thanks!
--
*********************************************************
David P. Both, RHCE
He/Him/His
*********************************************************
www.both.org - My personal web site
www.Linux-Databook.info - Home of the DataBook for Linux
DataBook is a Registered Trademark of David Both
*********************************************************
The value of any software lies in its usefulness
not in its price.
— Linus Torvalds
*********************************************************
On Thu, 18 Feb 2021, Ed Greshko wrote:
Date: Wed, 17 Feb 2021 21:11:12
From: Ed Greshko <ed.gres...@greshko.com>
Reply-To: Development discussions related to Fedora
<devel@lists.fedoraproject.org>
To: Steve Dickson <ste...@redhat.com>,
Development discussions related to Fedora <devel@lists.fedoraproject.org>
Subject: Re: Don't update to the latest f33!
On 18/02/2021 09:18, Steve Dickson wrote:
On 2/17/21 6:55 PM, Ed Greshko wrote:
On 18/02/2021 05:11, Steve Dickson wrote:
I agree... ignoring syntax error or parsing error just does not seem
like the appropriate thing to do... Error out! Tell me what is broken
so I can fix it!!
Replace the "," with a " " in the DNS= entry of
/etc/systemd/resolved.conf file.
And if you didn't format it that way, find out who did.
That is the question!!! I upgraded and DNS broke!
I didn't even know there was a /etc/systemd/resolved.conf
file until this unfortunate experience...
I know this won't make you feel any better. But the problem you've seen has
probably always existed
on your system but was "hidden" from view.
Previously the default for FallbackDNS as shown in /etc/systemd/resolved.conf
was
#FallbackDNS=1.1.1.1 8.8.8.8 1.0.0.1 8.8.4.4 2606:4700:4700::1111
2001:4860:4860::
8888 2606:4700:4700::1001 2001:4860:4860::884
But many folks complained that they didn't want a Fallback defined pointing
to Google or
other "services". So, it was removed and is now
#FallbackDNS=
Meaning none are defined.
So, previously, if your DNS= entry was incorrect you'd be protected by the
existence of the Fallback being
defined. Now, they are not.
So, whoever supplied the badly formatted /etc/systemd/resolved.conf file is
the "real" culprit.
If I recall, you're using a VM supplied by a vendor? If so, have you
notified them?
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
