Associate
- Joined
- 7 Jul 2007
- Posts
- 1,408
Done that but DNSSEC is still red?
You also need to turn trr.network.mode to 3 instead of 2.
This means the firefox will no longer fall back to the windows DNS resolver if the DNSSEC query fails.
Done that but DNSSEC is still red?
You also need to turn trr.network.mode to 3 instead of 2.
This means the firefox will no longer fall back to the windows DNS resolver if the DNSSEC query fails.
Is there a link which summarise benefits of dnssec, (I had to check) but ISP's still know what you are accessing
https://www.zdnet.com/article/dns-over-https-causes-more-problems-than-it-solves-experts-say/
I'm not debating the validity of the article as the author knows more than me on the subject. But one thing I will say is do they really? (ISP's know what you are accessing) Because when FireFox announced support for this technology there was a massive uproar from ISP's culminating with Firefox winning the 'Internet villain' of the year prize.
So exactly which part of the exchange can the ISP's see?
They cant see the DNS queries as they are encrypted and not using ISP DNS servers. Deep packet inspection will not get much back as the bits on the wire are encrypted.
That article seems muddled. Some are saying it's fake privacy whilst at the same time given an argument to the contrary.
At the end of the day I put my trust in this. Essentially it tells me no one listening on the wire can see my DNS queries.
Finally the address bar issue is resolved and I can view more than a handful of URLs. Just make sure that you set the number of rows for Top Sites to 2 or more.v79.0 is out.
Not sure why the need for a new version, nothing major seems to have changed.
Is there a link which summarise benefits of dnssec, (I had to check) but ISP's still know what you are accessing
https://www.zdnet.com/article/dns-over-https-causes-more-problems-than-it-solves-experts-say/