News for hackers. Stuff that matters.
Re:ICANN urges adopting DNSSEC now by the8472 on Saturday April 20, 2019 @01:42PM (#19707791)
DNS-over-TLS is only intended for stub resolver - recursive resolver traffic (check the introduction sections of the relevant RFCs). We're still lacking a protocol to provide confidentiality between the recursive resolver and authoritative servers. DNSCurve would offer that.
Re:ICANN urges adopting DNSSEC now by phicoh on Saturday April 20, 2019 @02:14PM (#19707987)
Which makes sense, because there is (in general) not much point in protecting traffic between recursive and auth. servers if you don't protect the stub resolver.

At the same time traffic between stub resolver and recursive resolver is much more privacy sensitive.

So it makes sense to first get TLS between stub and recursive up and running. And that proves already hard enough.

Re:ICANN urges adopting DNSSEC now by zzzcpan on Saturday April 20, 2019 @02:44PM (#19708173)
Technically stub resolvers and recursive resolvers are the same thing (one is an inherent part of the other). So all is needed is recursive resolvers to communicate securely with authoritative servers. Tunnels to third party recursive resolvers do nothing but leak private data to them.
Re:ICANN urges adopting DNSSEC now by the8472 on Saturday April 20, 2019 @05:36PM (#19709008)
But traffic to a recursive resolver can already be protected by other means, e.g. a tunnel to one that you control. There are zero options for contacting the authoritative ones.