failed to update records due to invalid txt record

[wilkejo]

What happened:

Our external dns deployment is triggered every minute and tries to create AWS Route 53 entries on our top level domain.

Logs:

Adding my-domain.com. to zone my-domain.com. [Id: /hostedzone/ABCD]
Adding my-domain.com. to zone my-domain.com. [Id: /hostedzone/ABCD]
Skipping record { Action: ""UPSERT"", ResourceRecordSet: { Name: ""_extdns.cname-my-domain.com"", ResourceRecords: [{ Value: ""\""heritage=external-dns,external-dns/owner=my-identifier,external-dns/resource=ingress/domain-prod/app\"""" }], TTL: 300, Type: ""TXT"" }} because no hosted zone matching record DNS Name was detected
Desired change: UPSERT _extdns.my-domain.com TXT [Id: /hostedzone/ABCD]
Desired change: UPSERT my-domain.com A [Id: /hostedzone/ABCD]
2 record(s) in zone my-domain.com. [Id: /hostedzone/ABCD] were successfully updated

This repeats every minute.

I assumes the error lies within the creation of the txt record with cname-my-domain.com which we do not own

What you expected to happen:

Do not try to update the records and do not create a cname-my-domain.com record. the record _extdns.cname-my-domain.com can not be created as we do not own cname-my-domain.com Log should sag All records are already up to date

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Container configuration

spec:
  containers:
  - args:
    - --log-level=info
    - --log-format=json
    - --interval=1m
    - --source=service
    - --source=ingress
    - --policy=sync
    - --registry=txt
    - --txt-owner-id=my-identifier
    - --txt-prefix=_extdns.
    - --domain-filter=prod-acc.cloud.my-domain.com
    - --domain-filter=subdomaina.my-domain.com
    - --domain-filter=subdomainb.my-domain.com
    - --domain-filter=my-domain.com
    - --provider=aws
    - --aws-zone-type=public

Environment:

• External-DNS version (use external-dns --version): registry.k8s.io/external-dns/external-dns:v0.13.6
• DNS provider: AWS Route53
• Others:

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[wilkejo]

We found this is an issue with 13.6. We downgraded to 13.5 and it is fine