Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

DNS over HTTPS and hosts file usage

  • 2 Mbohovái
  • 2 oguereko ko apañuãi
  • 4 Hecha
  • Mbohovái ipaháva konstantin2

more options

How does DNS over HTTPS modes define usage of hosts file?

Firefox: 69.0, OS: Ubuntu 18.04.3

I noticed that when I enable DNS over HTTPS ("network.trr.mode" set to 2 - use DoH, fall back to DNS), *and* hostname is defined in hosts file (/etc/hosts), Firefox usage of hosts file is inconsistent and hard to predict.

If IPs defined in hosts file and obtained via DNS request differ, corresponding site/resources behaves erratically, as if Firefox chooses at random, which page components' DNS address should be resolved via hosts, and which via DoH.

I had to disable DoH for that reason.

It is possible to set up DoH, so that it used hosts records, if present, and used DNS in all other cases?

How does DNS over HTTPS modes define usage of hosts file? Firefox: 69.0, OS: Ubuntu 18.04.3 I noticed that when I enable DNS over HTTPS ("network.trr.mode" set to 2 - use DoH, fall back to DNS), *and* hostname is defined in hosts file (/etc/hosts), Firefox usage of hosts file is inconsistent and hard to predict. If IPs defined in hosts file and obtained via DNS request differ, corresponding site/resources behaves erratically, as if Firefox chooses at random, which page components' DNS address should be resolved via hosts, and which via DoH. I had to disable DoH for that reason. It is possible to set up DoH, so that it used hosts records, if present, and used DNS in all other cases?

Opaite Mbohovái (2)

more options

It's puzzling that you get inconsistent results. Could it be due to cached DNS resolutions? Because otherwise it sounds as though Firefox is using the race mode (mode 1) instead of the fallback mode (mode 2):

  • 0 - local only, DoH off by default (current setting)
  • 1 - query DoH and local, use first available
  • 2 - query DoH first, fallback to local (checkbox in options)
  • 3 - query DoH only, do not use local (most private?)
  • 4 - use local but test DoH performance (temporary??)
  • 5 - local only, DoH off by user choice (won't be overridden??)

From: https://daniel.haxx.se/blog/2018/06/03/inside-firefoxs-doh-engine/

As far as I know, what you want is not an option, but I'm relying on the older definitions from the above blog post.

more options

I will try with

network.dnsCacheExpiration

set to 0 (if I understand your question correctly).

Pity the hosts file isn't taken into account as separate resolution means. In my case, when I need hosts-based IPs in certain circumstances, that means I should use a separate browser.