News for hackers. Stuff that matters.

A comment on Inside Firefox’s DNS-over-HTTPS engine. Parent comment

Re:Inside Firefox’s DNS-over-HTTPS engine by dtech on Monday June 04, 2018 @04:08AM (#17225554)
Using an alternative DNS resolver like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) could solve that already, and not only in Firefox.
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by flamemyst on Monday June 04, 2018 @08:07AM (#17226964)
That will not work. Some ISP do DNS transparent proxy (forward all udp packet 53 to their own DNS server). You need DNSCrypt or VPN.
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by stordoff on Monday June 04, 2018 @07:30AM (#17226754)
It depends how the block is implemented. If it's done by intercepting DNS requests, it doesn't matter what server you _try_ to reach. There's also the Virgin (UK) approach of allowing the correct DNS response, but tampering with HTTP requests (though switching to DNS-over-HTTPS wouldn't help in that case).
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by gsich on Monday June 04, 2018 @04:21AM (#17225623)
Or Quad9, but this could be intercepted.
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by xorcist on Monday June 04, 2018 @04:35AM (#17225697)
apt-get install unbound
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by codewithcheese on Monday June 04, 2018 @02:01PM (#17230340)
I was already using 1.1.1.1, did not unblock. Would be very curious if the ISPs were actually proxying my DNS requests. Any tips on how I might test that on Ubuntu?
[ Parent | on HN ]
Re:Inside Firefox’s DNS-over-HTTPS engine by eknkc on Monday June 04, 2018 @12:17PM (#17229354)
They generally inspect DNS packets and block hostnames from resolving correctly. Does not matter the destination.
[ Parent | on HN ]