Re: [Bundled-domain-names] A suggestion for 2017

[tjw ietf <[e-mail]>]

I would love to see a solid draft appear that discussed 'CNAME at APEX' in
an attempt to standardize what every vendor has been working on.



On Wed, Dec 28, 2016 at 4:17 PM, John Levine <[e-mail]> wrote:

> In article <[e-mail]> you write:
> >There have been many attempts to do something with the
> >bundle/alias/variant issue, often with proposals to improve/remplace
> >CNAME/DNAME/xNAME.
> >
> >One thing is missing: a repository of previous attempts, with
> >explanations of the problems they raise.
>
> That should be helpful, since people do seem to keep reinventing the
> same well known bad ideas (WKBI's).  The conclusion we came to at the
> most recent meeting is that almost all, and perhaps completely all, of
> the problems with provisioning variants can be solved with better DNS
> provisioning software, rather than looking for a magic DNS bullet that
> will solve the problem for us.
>
> > Case in point:
> >draft-sury-dnsext-cname-at-apex was published six years ago, saw
> >almost no discussion and expired. Why?
>
> This is an excellent case in point.  It attempts to solve the problem
> that you can't put a CNAME at the zone apex, by proposing an
> incompatible change to CNAME that lets it work at a zone apex.  An
> obvious failing is that there is no way to tell whether or not a
> server or cache supports new CNAMEs, so there's no way to deploy it.
>
> More importantly, we've already solved this problem by improving our
> provisioning software.  Lots of DNS systems let you say this in a zone
> file or equivalent:
>
> foo.example. ANAME bar.example.
>
> That tells the provisioning software to create A records for
> foo.example with the contents of the A records at bar.example.
> It polls now and then to see if bar.example has changed.
>
> On my system, I have a somewhat overimplemented scheme where
> I can say things like this:
>
>   IN A [RMTIP:bar.example]
>
> That means to replace the [RMTIP...] with records for with
> the contents of records at bar.example.  If there's more
> than one record it repeats the record, and as a special case, if
> there are AAAA records it creates AAAA records as well.
>
> www  IN  A   [RMTIP:www.example.org:ns1.somehost.com:A]
>
> That says to replace the [RMTIP...] with the A record(s) for
> www.example.org fetched from the name server at ns1.somehost.com.
> This solves an annoying problem when I have a web site hosted
> somewhere, the mail somewhere else, but the web host insists I use
> their nameservers, even though there's no way to put the required MX
> records on their nameservers.  Well, OK.
>
> This sort of provisioning stuff is not hard.  I added the RMTIP stuff
> to my system in an afternoon.
>
> R's,
> John
>
> _______________________________________________
> Bundled-domain-names mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/bundled-domain-names
>