This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Firefox launcher is blocked in slow DNS queries for local hostname

  • 3 respuestas
  • 1 tiene este problema
  • 1 visita
  • Última respuesta de mzabaluev

mzabaluev
mzabaluev
more options

I have got a dual-stack network interface configuration from one of Wi-Fi routers that provides the Linux PC with one IPv4 address and two IPv6 addresses. When this interface is connected, the Firefox launcher executable takes about 10 seconds to open a new window, even if the Firefox browser process is already running (and will be the process to open the window upon receiving an IPC from the launcher). IP packet capture and strace logs show that the launcher waits 5 seconds on two successive DNS queries trying to resolve A and AAAA records for the local hostname (as retrieved by e.g. "hostname" command). The hostname is not a FQDN, is locally assigned, does not match any DNS records and is not written into /etc/hosts; the DHCP configuration does not assign any domain name to the host either.

The IP addresses are assigned as follows: 

       inet 192.168.8.108  netmask 255.255.255.0  broadcast 192.168.8.255
       inet6 2001:999:50:fa22:6462:1479:f78:e78d  prefixlen 64  scopeid 0x0<global>
       inet6 2001:999:50:fa22:446e:e539:5727:6  prefixlen 128  scopeid 0x0<global>
       inet6 fe80::b425:e062:cddc:2aa4  prefixlen 64  scopeid 0x20<link>

/etc/resolv.conf is automatically generated as follows:

  1. Generated by NetworkManager

nameserver 192.168.8.1 nameserver fe80::466e:e5ff:fe39:5727%wlp3s0

There are some old bugs in Bugzilla (https://bugzilla.mozilla.org/show_bug.cgi?id=433665) making me suspect that it might be some fallback code that kicks in when multiple IP addresses are available for the local host. Is there a way to fix this behavior without hardcoding the IP addresses into system configuration files?

I have got a dual-stack network interface configuration from one of Wi-Fi routers that provides the Linux PC with one IPv4 address and two IPv6 addresses. When this interface is connected, the Firefox launcher executable takes about 10 seconds to open a new window, even if the Firefox browser process is already running (and will be the process to open the window upon receiving an IPC from the launcher). IP packet capture and strace logs show that the launcher waits 5 seconds on two successive DNS queries trying to resolve A and AAAA records for the local hostname (as retrieved by e.g. "hostname" command). The hostname is not a FQDN, is locally assigned, does not match any DNS records and is not written into /etc/hosts; the DHCP configuration does not assign any domain name to the host either. The IP addresses are assigned as follows: inet 192.168.8.108 netmask 255.255.255.0 broadcast 192.168.8.255 inet6 2001:999:50:fa22:6462:1479:f78:e78d prefixlen 64 scopeid 0x0<global> inet6 2001:999:50:fa22:446e:e539:5727:6 prefixlen 128 scopeid 0x0<global> inet6 fe80::b425:e062:cddc:2aa4 prefixlen 64 scopeid 0x20<link> /etc/resolv.conf is automatically generated as follows: # Generated by NetworkManager nameserver 192.168.8.1 nameserver fe80::466e:e5ff:fe39:5727%wlp3s0 There are some old bugs in Bugzilla (https://bugzilla.mozilla.org/show_bug.cgi?id=433665) making me suspect that it might be some fallback code that kicks in when multiple IP addresses are available for the local host. Is there a way to fix this behavior without hardcoding the IP addresses into system configuration files?

Todas las respuestas (3)

Shadow110
Shadow110
more options

Sorry, that is beyond me. Possibly everyone as no one has answered you.

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Try to ask advice at the Stack Overflow forum site.

There is a network.dns.localDomains pref available on the about:config page.

mzabaluev
mzabaluev Autor de la pregunta
more options

I have filed a bug on Bugzilla. I think the launcher behavior is wrong: it should not block on network queries in order to open a window, neither tweaking an obscure configuration preference is a good solution.