> It's also their intransigence re: SRV which has caused the CNAME at the > Apex issue. CNAME was *never* the right answer for doing application > level indirection in HTTP space.
SRV also trades CNAME at apex for wildcard names support. There is a plenty of services that employ wildcards to provide customized site for each user. For instance, userxyz.popularservice.test can be resolved via *.popularservice.test but equivalent setup with SRV would require _https._tcp.*.popularservice.test to work as a wildcard. _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
