Timeline for DNSSEC & DNSCrypt over Tor
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2019 at 4:42 | comment | added | Hikari | A ISP hardly will monitor and block DNS traffic leaving and returning on their network. This would add much more latency and support trouble than any blocking benefit for them. | |
| Aug 3, 2019 at 4:39 | comment | added | Hikari | To sum it up. There's even DNS-over-HTTPS solutions, but if you really have reason to be concerned, I'd suggest you have a local BIND server - or a full pihole, it's awesome, I now have one forwarding to my good-old BIND - forwarding to OpenDNS or something equivalent. Definitely don't use your ISP DNS for general sites, only for a few big CDN domains that it will point to its intranet servers. | |
| Aug 3, 2019 at 4:37 | comment | added | Hikari | lol I was asking something else and StackExchange suggested me this question, I read this answer and was gonna comment it, when I saw I was the one to do it! | |
| Mar 30, 2015 at 2:00 | history | answered | Hikari | CC BY-SA 3.0 |