GKE & Cloud DNS "No matching zone warning for record" messages for all root/apex domains

[thomascooper]

What happened: When using External-DNS 0.12.2 all A records and TXT records are created appropriately for subdomains (A record, matching TXT record, and a-[subdmain] TXT record). For a apex/root domain everything is created by the a-[root/apex domain] cannot be created, and every few minutes the pod logs spit out a warning for every single root/apex domain I have provisioned/configured.

What you expected to happen: I expect the system not log the warnings for a-[root/apex] domains, since that is never a possibility. We are migrating 10,000 zones over to external-dns managed, this would trigger 10,000+ erroneous logs every couple of minutes.

How to reproduce it (as minimally and precisely as possible): Deploy any root/apex domain

Anything else we need to know?: This did not appear to be an issue with 0.11 as I never saw these warning or the [type]-[subdomain] TXT records.

Environment:

• External-DNS version (use external-dns --version): 0.12.2
• DNS provider: GCP Google Cloud DNS
• Others: GKE Autopilot 1.21 Cluster

[dpoetzsch]

I can confirm this problem in 0.12.2 on GKE.

We have a zone for customer.example.com on GKE (actual domain redacted).

external-dns successfully creates all three records for domains below this zone, like sub.customer.example.com.

However, for customer.example.com only the A and TXT record is created, but not the a-customer.example.com record. The following message is repeated in the logs:

time="2022-10-06T17:17:03Z" level=warning msg="No matching zone for record addition: a-customer.example.com. TXT [\"heritage=external-dns,external-dns/owner=example-app,external-dns/resource=ingress/live/example-app-live-frontend-customer\"] 300"

I am not sure but think this might be a similar problem as described in #449 (comment)

[eyvind]

Why isn't the record type prepended to the existing --txt-prefix? It looks like I now have to modify --txt-prefix to add %{record_type}, but that seems like it would break the existing registry because the txt record prefix is different.

[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

[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

[k8s-triage-robot]

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

This bot triages 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:

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

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.