Re: [dnsext] Some thoughts on the updated aliasing draft

>But the reality is that the operators actually want the applications
>to treat two domain names as the same.  That's a lot harder than
>simply having the same IP returned when looking up an A record at
>each one.

This seems blindingly obvious to me, but I get the impression that
there is still a faction that thinks that if they can arrange for
matching A records, they're done.

>The only way around that that I can see at the moment is to either
>declare one record to be canonical (forcing applications to "correct"
>any names they are currently using to the canonical name) or use an
>additional layer of indirection so that all of the records that are
>the same point to some meta-target.

Agreed.  One point that I think is not well understood is that the
structure in the DNS and what the users see need not be perfectly
matched.  In particular, it's quite possible for the DNS to have one
canonical record with everything else pointing to it, but at the
application level all the names look the same.  If I were hacking on
my web or mail servers to handle this stuff, a simple way to do the
configuration would be to configure in the canonical name, and then
set a flag saying also to handle all of the aliases.

R's,
John
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext