5 ms·
I really do not understand why DNS was done so poorly. This could have been so much more simple and more secure in so many ways. Why can't I serve a HTTP heade
by 3pt14159 9y ago
I really do not understand why DNS was done so poorly. This could have been so much more simple and more secure in so many ways.
Why can't I serve a HTTP header or status code to update DNS? Why does propagation take hours when a simple pub-sub model would have worked and been a couple seconds of latency at most? How does DNS, something more important to get right than cryptographic certificates authorities, not come secure by default? How is it that a wildcard cert costs 10x as much as a TLD? Why does my browser not come pre-loaded with the top million DNS records? It would be a couple dozen megabytes (uncompressed).
The whole thing seems so stupidly put together.
- matthewmacleod 9y agoThe simple answer is because it was rolled out in the 1980s, far before the Internet existed in its current form. Hindsight is 20/20.
- stevekemp 9y agoRemember when DNS was created, and that answers your question. It's the same reason why FTP is terrible, and SMTP allows spoofing. The DNS protocol has been updated with additional record-types over time, but the protocol itself is largely unchanged since the time it was created, when the network was smaller, and the world was more trusting.