Ivan Ka
DNS lookups, not sure, on the edge. We all have different networking requirements, network segmentation, what if there is no access to DNS lookups and etc. Maybe we need a...
Got it. I'll submit a patch with documentation update. Yeah, handling apex corretly is not a trivial thing. The dns lookup could happen for example for domain `test.one.example.co.uk` from right...
So, the behaviour you described, could be a source or provider specific, as I was not able to reproduce it for AWS provider. There is an open issue from 2018.......
I've updated documentation. In regards `external-dns` to provide a migration path, there is a note that was there. I have tried to implement a migration, but there are no easy...
I just shared my configuration, and there is no problem I discover. Running on latest external-dns. The only different is AWS Route53, not cloudflare.
Have a look https://github.com/kubernetes-sigs/external-dns/pull/5172#issuecomment-2735479292. For apex domain, without even having a prefix, the new TXT record is `a-nginx-v2.ex.com`. There is no subdomain created.
I updated the docs. Personally not sure if docs update even need to be required, as not able to reproduce the behaviour in my setup, but no harm to have...
@mloiseleur I could be missing something obvious for apex domains. wdyt?
Understood. But this is a configuration that not default, so one could just break things. For example, if prefix contains IDNA character, example `點` this most likely will cripple/break records...
Nice one. Added to `docs/registry/txt.md`