On 3/25/21 10:21 AM, Michael Catanzaro wrote:
On Thu, Mar 25 2021 at 08:37:03 AM -0400, Robert Marcano via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
IMHO the fedora name should be always resolvable the same way as
localhost or just remove it. It is not right thsat fedora is being
resolved only while the DHCP server isn't assigning you a new hostname.
You never know when a DHCP server will decide to send you one,
especially if you move around many WiFi hotspots
The problem is not specific to the name "fedora" though. Our intended
behavior is to resolve the local hostname locally, without doing any
DNS, regardless of what its name is. This broke in Fedora 33 and you're
just the first person to notice and complain afaik.
Thank for looking at it. Without the broken VPN DNS and Firefox doing
some weird lookup at startup for the hostname I would have never noticed it.
I wonder if the Firefox thing has to do with their policies. Apparently
they have to be processed very early at startup and maybe there is
something in there slowing things down, but that would be another bug
than this one.
So editing /etc/hosts is not the right solution. We need to change our
NSS configuration. I'll send another mail about this.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
