On Mon, Sep 17, 2018 at 03:51:34AM +0000, Evan Hunt <e...@isc.org> wrote a message of 124 lines which said:
> I don't see how we can responsibly declare a new standard which, if > followed, will break every prior implementation. Apex CNAME is the > sort of solution that's clear, simple, and wrong. +1 > We're going to need another type code. Since the main use case is "people with a domain name such as example.com, who wants https://example.com/ to actually work, and who hosts the stuff at a CDN where the IP address is wildly variable so they cannot use A or AAAA records", I suggest that this use case is better solved by using SRV records for HTTP. True, it seems unrealistic that it will be specified and deployed but it is also the case for the DNS "CNAME at apex" change. _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
