Cover better for issues with CNAME flattening #150
Description
From Community Call on 3.2.2025:
[6.1] for Cloudflare there is an issue with CNAME flattening, especially on APEX.
[3.2] @kerolasa would like to have some "extension points" or language in the spec that would cover better for special handling needed to cover cases like CNAME flattening. A way forward would be to open an issue in GitHub and propose a text.
On a side note, there is a side effect also on txtPrefixMatching.
APEX CNAME would be resolved dynamically rendering the conflict prediction impossible. There might be a TXT record on origin side of CNAME or not. If there were one, there might be no possibility to remove such conflict other than removing the APEX CNAME as whole