On Fri, May 14, 2021 at 5:47 PM John Levine <jo...@taugh.com> wrote: > It appears that Brian Dickson <brian.peter.dick...@gmail.com> said: > >I said you weren't going to like it. > > No disagreement there. > > >I think it should be taken as a safe assumption, that for the vast > majority > >of end users, they will either be using some kind of UI (good, bad, or > >ugly) that is (eventually) aware of the relevant RRTYPE(s), or using one > or > >more tools that do validation of the zone file (as part of the process of > >adding new records), or using software for serving the zone(s) which does > >the necessary checks as part of the start-up or zone-loading process (and > >prevents illegal stuff, including things like "CNAME and other RRTYPE at > >same owner name", or "Multiple CNAMEs at same owner name". > > Perhaps, or in a lot of cases, the web hosting provider gives the customer > the > DNS records to copy and paste into their DNS provider's console. >
While it may not have yet achieved ubiquitous use in the web hosting space, DomainConnect is a method used by quite a few providers, and supported by a number of DNS providers. DomainConnect uses a template mechanism, where the service provider (in this case, web hosting provider) supplies values that correspond to variable in the template. In that particular use case, having a template that has simple encoding makes the interoperability much more reliable. The biggest benefit of using a scheme with one key/value pair per line, is the substitution is dead easy. No escaping or quoting problems. It isn't necessarily meant to be read by the user, but if they choose, it is visible. (The particulars of DomainConnect are basically, the service provider has a UI thing that takes the user to an auth page for the DNS provider, and after authenticating, magic happens.) Brian
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
