Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It has taken two decades to get to this point. The protocol has been substantially revised four times, and, after each of those four revisions, DNSSEC proponents said "now, we've got it right, and it's ready for universal deployment".

It is nowhere near ready for universal deployment today, and, indeed, virtually nobody relies on it, unlike TLS.



DNSSEC ain't pretty. I'll agree with you there, but that doesn't mean it isn't the best thing going for us in terms of securing the DNS. Like it or not it's important to be able to trust DNS responses.

I guess I don't have some expectation that deployment should take place quickly. Or that the first go at a protocol is going to always get it right. Just because a journey is difficult doesn't mean the journey isn't worth taking.

DNSSEC and TLS are unrelated. They're trying to solve different problems.


There is no point to securing the DNS. There are only downsides.


*using DNSSEC


I don't think there's any point to securing the DNS at all.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: