News for hackers. Stuff that matters.
Re:DNS Privacy Considerations by netr0ute on Saturday July 31, 2021 @09:37AM (#28018019)
That's why you block port 53 in both UDP and TCP so nothing can bypass it. I also block most known DoH servers outright.
Re:DNS Privacy Considerations by tremon on Saturday July 31, 2021 @10:28AM (#28018424)
I also block most known DoH servers outright.

When someone hosts a DoH server on a cdn/AWS/Azure/Google shared IP address, you can't block it by IP; and if the client uses ESNI, you can't block it by HTTP header inspection either.

Re:DNS Privacy Considerations by netr0ute on Sunday August 01, 2021 @06:25PM (#28030739)
How will the client know what address to send DoH to? You wouldn't just hardcode an IP unless you want that predictable address manually blocked in the firewall.
Re:DNS Privacy Considerations by silon42 on Saturday July 31, 2021 @10:18AM (#28018334)
Also need to block all hosts not allowed by your own DNS server. Also need to give each "untrusted" app a separate local IP (in future: must have NAT for IPv6 too).
Re:DNS Privacy Considerations by silon42 on Saturday July 31, 2021 @10:29AM (#28018435)
Or just force the use of HTTP/S proxy.
Re:DNS Privacy Considerations by Havoc on Saturday July 31, 2021 @11:06AM (#28018739)
>That's why you block port 53 in both UDP and TCP so nothing can bypass it.

Already done...something is still sneaking through...or cloudflares test is unreliable (or my iptables rules are wrong lol)