Did you not read my full message? I didn't say don't do that, I said let's do it in an elegant way. Then I provided a few examples of how to do that.
I'll defer to other people, but it seems to me that anything that depends on recursive DNS servers being updated isn't a realistic solution. We're still waiting for DNSSEC, after all.
What is being done now is not ANAME by any stretch; it is vertically-integrated apex CNAME flattening.
My version periodically fetches the remote A and AAAA records, invents local A and AAAA records, and signs them. It's a kludge, but it gets the job done.
With respect to the whole anycast and CDN thing, it is not my impression that ANAME hacks are widely used for big sophisticated sites. Mine are used for small biz sites where my user wants to use my mail but someone else's web service.
Can you point me to a non-closed, non-vertically-integrated ANAME-like thing that offers interoperable multi-vendor support?
Of course not. That's why we're talking about ANAME. Regards, John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY Please consider the environment before reading this e-mail. https://jl.ly _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
