Geolocalization dies with CNAME flattening. Several CDNs answer different sets of As depending on client (or resolver's client) location. That is not possible if you flatten in the CNAME at the origin. You have to choose one point of view, or use several and send a union of all As, and let the browser sort it out. Which I think they can't.
Hugo On October 23, 2024 2:38:40 AM GMT-03:00, Peter Thomassen via dns-operations <dns-operati...@dns-oarc.net> wrote: >_______________________________________________ >dns-operations mailing list >dns-operations@lists.dns-oarc.net >https://lists.dns-oarc.net/mailman/listinfo/dns-operations _______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations