You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a webhook provider. Underlying DNS provider rejects trying to create CNAME and TXT record of the same name (which abides by the RFC AFAIR). However I see that it attempts to create both old-style and new-style DNS TXT records:
What happened:
I'm developing a webhook provider. Underlying DNS provider rejects trying to create CNAME and TXT record of the same name (which abides by the RFC AFAIR). However I see that it attempts to create both old-style and new-style DNS TXT records:
test.example.com
-->"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/default/test"
cname-test.example.com
-->"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/default/test"
New-style records are created just fine (as they don't conflict with CNAME).
However, on the next run it still tries to create old-style records (as
txt/force-update
:true
provider-specific property has been assigned)What you expected to happen:
Registry is constructed from new-style records only; absence of old records is discarded
How to reproduce it (as minimally and precisely as possible):
WIP
Anything else we need to know?:
I believe the fix would be to either:
Environment:
external-dns --version
):unknown
(f5545b1e164776958fbb85ed055ae418fb0f24dc
)The text was updated successfully, but these errors were encountered: