Feature request: Encrypted and validated DNS via DNSSEC

Features & Priorities

Last Post by Random 4 Jahren ago

5 Posts

5 Users

18 Reactions

1,311 Views

RSS

19/01/2020 9:50 pm

Topic starter

markus.elbblocker

(@markus-elbblocker)

Member

3 Posts
3 0 0

Just an idea for a bit more privacy: The eBlocker could use DNSSEC to serve domain name resolution. Unbound cloud manage this as an additional local DNS resolver that delivers queries to DNSSEC aware public resolvers like 9.9.9.9. We would also benefit from validated DNS replies.

Answer

ovflowd 04/03/2020 11:11 am

This sounds a really good idea. Either DNSSEC or DNSCrypt would be good extra options 🙂

DNSCrypt has the advantage of allowing any DNS server to become "DNSSEC-able". 😀

Random 04/03/2020 9:56 pm

@ovflowd

Sounds great! If you are the expert, move forward and implement it 🙂

Topic Tags

DNSSEC DNS

1 Answer

09/03/2020 2:54 pm

Invisible

(@invisible)

New Member

2 Posts
0 2 0

I absolutely support the secure DNS feature request.Protection against eavesdropping and tampering are just the next logical step to protect our privacy and stop sophisticated malware attacks.

I prioritize security & privacy features above reporting/logging/UX improvements.

johann0815 13/02/2021 7:43 pm

I just wanna push this great idea! 🙂

would be great if it’s possible to use a secure dns with doh, dot or Dnscrypt

thank you!

Random 18/03/2021 8:55 pm

@johann0815 Personally I don't like to get pushed 😉 If you wanna push it: just implement it. eBlocker is a community effort and open source. So I'm looking forward to your pull request - not pushing 😜

Add a comment

Answer