top | item 24008285

DNSSEC explained: Why you might want to implement it on your domain

19 points| c0r0n3r | 5 years ago |csoonline.com | reply

14 comments

order
[+] SimeVidas|5 years ago|reply
I’m a simple man. Website shows fullscreen popup that interrupts me and also scrolls the page to the top. I close the tab.
[+] brightball|5 years ago|reply
Would be a worthwhile article to read if it wasn't pay walled.
[+] MayeulC|5 years ago|reply
The article is behind a paywall, but more to the point: why wouldn't I want this?

It's opt-in at every registrar I've used, although it seems like a no-brainer to me? What am I missing?

As an aside, I like DoH, but dislike the fact that my web browsers then don't use /etc/hosts. Is there a way to provide it at the system level?

[+] xythian|5 years ago|reply
I'd love to know why some of the major companies of the internet aren't using DNSSEC.

Google, Amazon, Facebook, Twitter, Microsoft, Netflix, etc. don't have DNSSEC enabled for their domains.

Is it as simple as they're just concerned about the occasional DNS request failing to do DNSSEC issues and thus reducing precious traffic?

[+] Whatarethese|5 years ago|reply
Can anyone put this on pastebin or something? Paywalled.