zlacker

[return to "Windows 11 Officially Shuts Down Firefox’s Default Browser Workaround"]
1. jhoelz+xa[view] [source] 2021-12-16 17:13:34
>>beezle+(OP)
I have a feeling that MS is playing with fire again....

That every request made through the edge browser for a non local user is associated to his/her live ID is pure coincidence ;)

Sometimes when I look into my dns logs, I cry a little bit inside too.

◧◩
2. Datage+8q[view] [source] 2021-12-16 18:13:54
>>jhoelz+xa
That's the moment you fire up Firefox without prefetch nor studies and enjoy the peaceful DNS logs without the constant telemetry calls to LinkedIn and to all interested 3rd parties, five eyes etc
◧◩◪
3. jhoelz+ts[view] [source] 2021-12-16 18:23:27
>>Datage+8q
i thought that too!

but firefox has different dns requests going to their servers as well.

◧◩◪◨
4. no_tim+W01[view] [source] 2021-12-16 21:04:34
>>jhoelz+ts
On linux you can use IceCat. On windows, download simplewall and block pingsender.exe there. Should get rid of the queries if you combine it with userjs tweaking.
◧◩◪◨⬒
5. callam+sd1[view] [source] 2021-12-16 22:09:09
>>no_tim+W01
Just setup pihole - you can run it on any server and use it as a local dns server. Probably somebody else has done the work to list these spammy domains.
◧◩◪◨⬒⬓
6. paulry+9j1[view] [source] 2021-12-16 22:46:15
>>callam+sd1
What about DNS over HTTPS?
◧◩◪◨⬒⬓⬔
7. zamada+KU1[view] [source] 2021-12-17 03:31:46
>>paulry+9j1
If you just want FF to not use it you can block "use-application-dns.net" which acts as a canary domain for it to disable DoH.

If you want to block it from things you don't trust to have such methods (or always listen to them) you'll have to upgrade to a firewall that can filter outbound connections to IPs the client hasn't received a DNS response for or require use of an explicit HTTP proxy for outbound connectivity.

Just blocking DNS can be a good middle ground for reasonable effectiveness without as much effort.

[go to top]