4 ms·

After setting the log level, where do I see the log? I think -safe-mode disables all extensions. No snap, just FF. Amazingly, it even happens when I install a

After setting the log level, where do I see the log? I think -safe-mode disables all extensions. No snap, just FF. Amazingly, it even happens when I install a fresh version of FF in a docker container! Maybe some update hit that is doing some funky network stuff that is slow via my router or something? Hmm... FF starts immediately if I disconnect from the network first. That seems to support the last idea. Seems to be some kind of DNS issue. When I replace my /etc/resolv.conf file with a file that contains only this: nameserver 8.8.8.8 options edns0 trust-ad The delay goes away. Before there was also: nameserver 127.0.0.53 options edns0 trust-ad search <hostnameofmyrouter> No idea what 127.0.0.53 is. Is there a DNS server running on my laptop? And also not sure what "search" does.

tinus_hn 4y ago
127.0.0.53 is the proxy dns server run by systemd. Search specifies one or more domains, for instance ‘domain1.com’, and then if a program tries to resolve ‘host1’ if that doesn’t work it’ll also try ‘host1.domain1.com’. That way you can give your router for instance the host name router.domain1.com and it’ll work if you type ‘ping router’.
- JonathanBeuys 4y ago
  The proxy is in place to cache dns queries? And which dns server does the proxy dns server connect to?
  - tinus_hn 4y ago
    No. I’m no systemd expert but as far as I know the idea is that the resolv.conf configuration system was designed decades ago when you’d have a Unix system connected through cable to a network run by an expert. But a modern system might be wirelessly connected to many different networks through time or even at the same time, with many of them not run by consumers who have no idea what they’re doing. So there’s a mismatch. The earlier solution was dhcp clients editing resolv.conf to include the configuration they get from the dhcp server. But that doesn’t really work if it changes all the time, if you want to have a different manual configuration for some networks or if you are connected to multiple networks at the same time. Systemd tries to make it possible to configure this in a modern way and the idea is that most applications (that use the system libraries in the typical way) don’t use resolv.conf at all but talk to a part of systemd to resolve queries with that part using modern configuration. Other legacy applications that try to parse that file or use the configuration in another way find a proxy dns server run by systemd that gives them the same answers the other applications get.

tinus_hn 4y ago

127.0.0.53 is the proxy dns server run by systemd. Search specifies one or more domains, for instance ‘domain1.com’, and then if a program tries to resolve ‘host1’ if that doesn’t work it’ll also try ‘host1.domain1.com’. That way you can give your router for instance the host name router.domain1.com and it’ll work if you type ‘ping router’.

JonathanBeuys 4y ago
The proxy is in place to cache dns queries? And which dns server does the proxy dns server connect to?
- tinus_hn 4y ago
  No. I’m no systemd expert but as far as I know the idea is that the resolv.conf configuration system was designed decades ago when you’d have a Unix system connected through cable to a network run by an expert. But a modern system might be wirelessly connected to many different networks through time or even at the same time, with many of them not run by consumers who have no idea what they’re doing. So there’s a mismatch. The earlier solution was dhcp clients editing resolv.conf to include the configuration they get from the dhcp server. But that doesn’t really work if it changes all the time, if you want to have a different manual configuration for some networks or if you are connected to multiple networks at the same time. Systemd tries to make it possible to configure this in a modern way and the idea is that most applications (that use the system libraries in the typical way) don’t use resolv.conf at all but talk to a part of systemd to resolve queries with that part using modern configuration. Other legacy applications that try to parse that file or use the configuration in another way find a proxy dns server run by systemd that gives them the same answers the other applications get.