News for hackers. Stuff that matters.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by protomyth on Wednesday April 10, 2019 @12:41PM (#19626421)
So, the internal domain names leak to Mozilla unless I disable this totally?
Re:DNS-over-HTTPS Policy Requirements for Resolvers by cpeterso on Wednesday April 10, 2019 @12:49PM (#19626507)
Not to Mozilla, but to whichever DoH service Firefox is configured to use, by default or by the user. Mozilla isn't running a DoH service.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by protomyth on Wednesday April 10, 2019 @01:41PM (#19627027)
What is the default?
Re:DNS-over-HTTPS Policy Requirements for Resolvers by moosingin3space on Wednesday April 10, 2019 @02:04PM (#19627236)
Cloudflare 1.1.1.1 is the default.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by protomyth on Wednesday April 10, 2019 @02:19PM (#19627378)
So, when the user types in internal.mydomain.com, it gets sent to Cloudflare then they query my public domain server which doesn't have the entry so it falls back to checking the DNS the system has listed. Is Firefox going to cache the IP like the OS does?
Re:DNS-over-HTTPS Policy Requirements for Resolvers by moosingin3space on Wednesday April 10, 2019 @02:29PM (#19627473)
The behaviour depends on a few preferences:

* network.trr.mode can be set to 0 (disabled), 1 (race native vs TRR), 2 (TRR first, OS DNS as fallback), 3 (TRR only), 4 (run native and TRR in parallel but use native results, save TRR timings for telemetry), or 5 (off by choice)

* network.trr.uri configures which DoH endpoint is queried

Firefox does maintain a DNS cache, even if you use the native DNS resolver. You can view the cache at about:networking#dns.

Re:DNS-over-HTTPS Policy Requirements for Resolvers by protomyth on Wednesday April 10, 2019 @11:21PM (#19630888)
So, I really need to set 5 because 0 will probably later become default consent to use DNS-over-HTTPS.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by xorcist on Wednesday April 10, 2019 @02:42PM (#19627576)
To be fair, can anyone really expect otherwise?

If you insist on using a third party resolver for name resolution they will have knowledge of your queries no matter what the protocol. Doing it over tcp and http is not any better, or worse, than doing it over udp. This is something you have to opt in to.

Re:DNS-over-HTTPS Policy Requirements for Resolvers by protomyth on Wednesday April 10, 2019 @02:44PM (#19627589)
> This is something you have to opt in to.

Does it come turned off by default?

Re:DNS-over-HTTPS Policy Requirements for Resolvers by bzbarsky on Wednesday April 10, 2019 @05:59PM (#19629191)
DNS-over-HTTPS in Firefox? Yes, it does, at the moment. See https://searchfox.org/mozilla-central/rev/dd7e27f4a805e4115d... -- 0 means it's off.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by stock_toaster on Wednesday April 10, 2019 @06:16PM (#19629300)
5 is "off by choice"
Re:DNS-over-HTTPS Policy Requirements for Resolvers by bzbarsky on Thursday April 11, 2019 @10:52AM (#19635056)
Yes, the difference is that 0 is the default value right now, so if you set it in about:config all Gecko remembers is "it's the default" and stores nothing in user.js; if the default then changes the value changes.

5 is not the default, so if you set it it will get stored in user.js and then even if the default changes the value will remain 5.