On 3/24/21 9:51 PM, Robert Marcano wrote:
Currently I am connecting to a VPN that provides a few DNS search
entries. One of these domains on the search path is having DNS
resolution problems. This is not per se the the problem I am writing
this email for.
The problem is that starting Firefox and Thunderbird take a long time,
it took time to detect the DNS resolution problem was the origin of
these timeouts. I am not using that domain that is having resolution
problems.
The real culprit is the default `fedora` hostname, instead of localhost.
Starting a Wireshark capture there are DNS searches for
fedora.domain_failing.tld, when starting Firefox and Thunderbird. The
presence of the search path on generated /etc/resolv.conf isn't the
cause of these DNS searches, I edited them out while the VPN was still
active.
Even 'ping fedora' start doing these searches with the search paths
appended. 'ping localhost' doesn't do that. The only workaround to this
issue is to add fedora to the localhost entries on /etc/hosts.
This in some way is a DNS leak, even on a VPN with perfectly working DNS
resolution, the fedora name should not be searched on these domains
until I am using the fedora full hostname on these domains. Even worse
when simply starting applications like Firefox o Thunderbird.
Maybe changing the default hostname to fedora wasn't a good idea after
all, or at least fedora should be added to the default /etc/hosts.
About the default fedora transient hostname nchange. This has caused
more problems that really solved.
Sometime ago the default HOSTNAME environment variable was changed to
use in /etc/profile
HOSTNAME=`/usr/bin/hostnamectl --transient`
This didn't cause any problems initially because the the default was
localhost.localdomain, but now that is fedora. If you reach the desktop
before plugin in your laptop to the network and your network DHCP server
assigns you a hostname, you get a entire session where the HOSTNAME
isn't resolvable, because fedora is only resolvable when the transient
host name was set as fedora, but it was overriden by the DHCP server.
Tilix was one of the programs with problems with this, you get an
annoying warning. I solved this by adding HOSTNAME=`hostname` to .bashrc
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
_______________________________________________
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
