Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Reproducible slow (30 seconds) DNS resolution on Ubuntu 24.04

  • 8 个回答
  • 1 人有此问题
  • 8 次查看
  • 最后回复者为 TyDraniu

more options

I use Firefox 134.0.2 (64-bit) on Ubuntu 24.04.

Some (not all) web sites show up only after a delay of exactly 30 seconds. The attached screenshot shows that this delay is due to DNS resolution. This behavior is reproducible by simply closing Firefox, opening it again and entering the same web site once more. Once this initial delay of 30 seconds for DNS resolving has passed the web site can be browsed normally.

Using Google Chrome, Opera or even the Tor Browser on the same system works without any significant delay. Also a DNS lookup from the console returns data almost immediately.

As the delay is always exactly 30 seconds this looks like some DNS resolver timeout only showing up when using Firefox.

Neither starting Firefox in Troubleshoot Mode nor (as often suggested) disabling IPV6 for DNS by setting network.dns.disableIPv6 to true did help.

Any idea how to fix this 30 seconds delay?

Many thanks for any help, Felix

I use Firefox 134.0.2 (64-bit) on Ubuntu 24.04. Some (not all) web sites show up only after a delay of '''exactly''' 30 seconds. The attached screenshot shows that this delay is due to DNS resolution. This behavior is reproducible by simply closing Firefox, opening it again and entering the same web site once more. Once this initial delay of 30 seconds for DNS resolving has passed the web site can be browsed normally. Using Google Chrome, Opera or even the Tor Browser on the same system works without any significant delay. Also a DNS lookup from the console returns data almost immediately. As the delay is always exactly 30 seconds this looks like some DNS resolver timeout only showing up when using Firefox. Neither starting Firefox in ''Troubleshoot Mode'' nor (as often suggested) disabling IPV6 for DNS by setting ''network.dns.disableIPv6'' to ''true'' did help. Any idea how to fix this 30 seconds delay? Many thanks for any help, Felix
已附加屏幕截图

所有回复 (8)

more options

Has it started recently to behave this way? Is it a regression?

有帮助吗?

more options

I'm pretty sure it started 2 to 4 weeks ago. I have not seen this before.

有帮助吗?

more options

Can you test it with mozregression? It would be helpful to find a commit that broke it.

有帮助吗?

more options

Thanks for the tip! I have attached a screenshot from the bisect result and this is the contents of the build info window:

app_name: firefox build_date: 2024-12-03 14:55:16.908000 build_file: /home/felix/.mozilla/mozregression/persist/fb9f6b58f4db-pgo--autoland--target.tar.xz build_type: integration build_url: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/LjYzS4xTTv-8LTCa4-fY8g/runs/0/artifacts/public%2Fbuild%2Ftarget.tar.xz changeset: fb9f6b58f4db1dd50bd71e1c8b65238efe6386b4 pushlog_url: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=5b8d2c7e3f1f707f7fd8cea7c7eabd86e0abd3f0&tochange=fb9f6b58f4db1dd50bd71e1c8b65238efe6386b4 repo_name: autoland repo_url: https://hg.mozilla.org/integration/autoland task_id: LjYzS4xTTv-8LTCa4-fY8g

If useful I can provide the entire bisecting log.

有帮助吗?

more options

Thanks, this bug is secured, I don't really know what's going on there, it's something about mismatched NPN token.

As a test, try to go to about:config and switch security.ssl.enable_alpn to false + restart.

PS. I've reached to the Network team, I hope they will say something about it.

由TyDraniu于修改

有帮助吗?

more options

Sadly disabling ALPN did not help, thanks anyway. Just for testing, I also temporarily disabled the HTTPS record in the DNS server. This too did not help.

Let me know if there is anything else I can contribute to fix this problem.

有帮助吗?

more options

Concerning the influence of the DNS HTTPS record being present or not, the statement in my previous post was wrong, sorry. As usual I had not enough patience when playing with DNS entries.

The 30 seconds delay with Firefox occurs only when the HTTPS record is present in the DNS. If the HTTPS record in the DNS is missing, Firefox is as fast as Google Chrome.

Just in case, the HTTPS record looks like this: www.ltec.ch. 3600 IN HTTPS 10 . alpn="h3,h2"

有帮助吗?

more options

Ah, OK. Everything is clear now.

https://bugzilla.mozilla.org/show_bug.cgi?id=1943011

有帮助吗?

我要提问

您需要登录才能回复。如果您还没账号,可以提出新问题