Re:Chromium's impact on root DNS traffic (2020)
by tptacek on Wednesday February 08, 2023 @09:13AM
(#34708234)
We are nowhere even in the perceptible range of "completely overwhelming" the root servers.
Re:Chromium's impact on root DNS traffic (2020)
by mschuster91 on Wednesday February 08, 2023 @09:43AM
(#34708650)
> Perhaps we need new record types to support this?
The solution would have been DNSSEC, the problem is that authenticating NXDOMAIN responses comes with a ton of challenges on its own and so there, in the end, was just workarounds and messy hacks [1] that IIRC no one ended up utilizing.
[1] https://en.wikipedia.org/wiki/Domain_Name_System_Security_Ex...
Re:Chromium's impact on root DNS traffic (2020)
by tptacek on Wednesday February 08, 2023 @09:46AM
(#34708692)
No, it's not! The problem here is end-users being forced to trust their upstream DNS caches. DNSSEC doesn't change that! It's a server-to-server protocol, so the same NXDOMAIN interception problem exists --- the intercepting DNS server just sets the AD bit in the header. You can run DNSSEC directly from an end-system, bypassing caches --- but then, relieving load on the roots (a non-issue, but still) is right out the window.
Re:Chromium's impact on root DNS traffic (2020)
by sumtechguy on Wednesday February 08, 2023 @12:24PM
(#34711395)
You are right. My brain decided to forget that existed!
That the browsers are reacting in this way says we have a failure at the DNS software level. Those projects do seem to be giving the security that is wanted. So we are starting to get some fragmentation. Which can not be good. Perhaps we need new record types to support this?