Systemd-resolved DNS config change leads to huge start delays in some programs

Ask Fedora
, ,
1

Hello everyone.
I recently changed my /etc/systemd/resolved.conf to the following:

[Resolve]
DNS=1.1.1.1 1.0.0.1
DNSOverTLS=yes

With these changes, the system runs absolutely fine and uses the correct nameservers (checked with Wireshark). But I have the following problems that I simply cannot understand:

  • the os fails to resolve invalid domain names like any.abc with the following output with dig:
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out

; <<>> DiG 9.18.26 <<>> any.abc
;; global options: +cmd
;; no servers could be reached

This does not happen with the default empty config.

  • some programs, including firefox, thunderbird, or any forks of them, and for example the telnet client have a huge 5min start delay if they have access to unix sockets (tested with a firejail config without protocol unix.

Does anyone have any idea what the problem could be?
Many thanks in advance!

1 Like
2

This fix worked. Sorry for bringing this up again.

3

There’s a more generic method:
DNF and Firefox take extreemly long to start when VPN active on f40? - #4 by vgaetera