Mike Eves

It feels wrong to be continuing forward moving to the newer TXT format and removing the legacy format given the [issues](https://github.com/kubernetes-sigs/external-dns/issues/3757) with the new format. Right now with the dual...

I agree, the TXT registry has been a bit of a mess for a while now, ever since the new format was introduced to help support managing the same record...

Our setup has the below flags: ``` - --source=ingress - --source=service - --source=crd - --provider=cloudflare - --policy=sync - --registry=txt - --txt-owner-id=dpp - --annotation-filter=external-dns.alpha.kubernetes.io/ignore notin (true) - --crd-source-apiversion=externaldns.k8s.io/v1alpha1 - --txt-prefix=prefix. ```...

> I think the question is, how to reliably `determine if zone apex or subdomain`....... The way we've handled a similar problem elsewhere (determining the authoritative zone for a domain)...

I suppose even if you could reliably determine a domain is an apex, what would external-dns do to handle the domain differently? You could suffix it with a period `.`...

> So, the behaviour you described, could be a source or provider specific, as I was not able to reproduce it for AWS provider. The problem exists when a user...

@ivankatliarchuk If you try with `--txt-prefix=foo.` you should be able to see the issue I would imagine

The README already contains this: > If using a txt registry and attempting to use a CNAME the --txt-prefix must be set to avoid conflicts. Changing --txt-prefix will result in...

@cgroschupp Are you still planning to continue with this PR? @johngmyers Were the changes required to account for https://github.com/kubernetes-sigs/external-dns/pull/3910 the only outstanding actions stopping this being merged? Keen to see...

/remove-lifecycle stale