3 ms·
The major providers also “gave up” on SRV records for HTTP/2, but that does not make it a bad idea – on the contrary, SRV for HTTP would be a good idea for the
by teddyh 8y ago
The major providers also “gave up” on SRV records for HTTP/2, but that does not make it a bad idea – on the contrary, SRV for HTTP would be a good idea for the rest of us. But not for Google, since not having it cements their position.
> But in the long term, DNS is going to get factored out of domain verification entirely. CAs will eventually (who knows how long it will take, even though the protocols are there) just verify domains directly with registrars using something built on RDAP.
Get back to me when that actually happens, or looks likely to ever happen. Last I heard, the proposed replacement of WHOIS with RDAP has been put on very thick ice, and it is uncertain what will actually happen.
> It's hard to see the justification for rolling out [DNSSEC] (…)
In my world, that ship has long sailed. DNSSEC is fully rolled out. I work for a domain name registrar, and more than 30% of all the domains we manage are DNSSEC signed, and we could easily sign another 30% if we wanted to.
DNSSEC has long been rolled out. It’s too late to argue that it shouldn’t be.
- tptacek 8y agoPeople have been claiming DNSSEC is "rolled out" for almost a decade now (amusingly, they said so before the major TLDs were even signed). You're missing the point: nobody uses it. No major tech company even signs their zone. The browsers don't do DNSSEC lookups --- Firefox and Chrome actually removed their support for it. People affiliated with registrars are constantly pointing out how many zones they sign, as if that was any kind of argument at all. Look, nobody doubts that you can build a feature into your stack that automatically signs zones. 30%? Why not 100%? Who cares? That's just theater. What matters are companies actually relying on the protocol. Nobody does, today.