Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderThere are at least two more arguments against DNSSEC: 1) DNSSEC does materially make DDOS reflection attacks worse. djb has gone on about this at length, so I won't. 2) DNSSEC also degrades a DNS server's ability to respond to requests. A regular non-DNSSEC DNS server can look up responses in O(1) time; see djb's TinyDNS for an example (it uses a CDB hash table to do it). A DNSSEC server must either use an ordered index to find "nearest…
Just checked Faang and none of them have DNSSEC enabled: for d in Amazon.com Facebook.com Apple.com Google.com Netflix.com ; do delv "$d" @1.1.1.1; done
Please don't use things I wrote as a coatrack to hang advertisements of your blockchain DNS replacement.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 257
- Total comments
- 248
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2015-01-15 | Against DNSSECFirst breakout · Best thread | tptacek | 186 | 144 |
| 2016-07-25 | Why DNSSEC brings more problems than it solves (2015) | vladaionescu | 3 | 0 |
| 2019-11-10 | DNSSEC Is Unnecessary | pmoriarty | 2 | 0 |
| 2020-03-30 | Against DNSSEC | rasengan | 2 | 2 |
| 2021-05-10 | Against DNSSEC (2015) | mvolfik | 2 | 0 |
| 2021-10-01 | Against DNSSEC (2015) | trulyrandom | 1 | 0 |
| 2022-10-21 | Against DNSSEC (2015)Hall induction · Latest 20+ point return | tosh | 56 | 102 |
| 2025-09-07 | Against DNSSEC (2015) | mcdonje | 4 | 0 |
| 2026-05-06 | Against DNSSEC (2015) | jamilbk | 1 | 0 |