3 ms·
HTTPSSVC might, as a side effect, finally solve the problem of not being able to point the root of a domain (eg 'google.com') to a CDN. (although the rollout o
by unilynx 6y ago
HTTPSSVC might, as a side effect, finally solve the problem of not being able to point the root of a domain (eg 'google.com') to a CDN.
(although the rollout of HTTPSSVC to all DNS servers and domain hoster APIs will probably take even longer than the phase-out of IE..)
- _wldu 6y agoIsn't that because CNAMES may not be combined with other records and SOA and NS are required on whatever.com? https://tools.ietf.org/html/rfc2181 https://tools.ietf.org/html/rfc2181
- unilynx 6y agoYep. There was talk of ANAME records at IETF but that doesn't seem to be really going somewhere Some DNS servers implement something they often call ALIAS, but it's basically the equivalent of having a crontab mirror the settings of the records you're referring to, and breaks eg. geo-dependent address resolving (so not that useful for referring to a CDN, which is why you'd most likely want this)
- corty 6y agoSRV records would already support that is browsers would look them up. But unfortunately they don't.
- EvanAnderson 6y agoI wish SRV records had been adopted widely. It would be a much nicer world.
- pas 6y agoThat's the [new] hope with SVCB. https://blog.cloudflare.com/speeding-up-https-and-http-3-negotiation-with-dns/ https://blog.cloudflare.com/speeding-up-https-and-http-3-neg...
- xfalcox 6y agoI can't wait to see browser support for HTTPSSVC. - CNAME in the apex domain - Direct HTTP/3