PDNS (PowerDNS) "No matching zones were found for the following endpoints" trying to create zones with an "a-" prefix

[darkpixel]

What happened:
I've been ignoring this error for years now, but it's been getting more and more annoying when I parse through logs.
If I have a domain example.tld, external-dns will configure it properly with whatever A records I need.

During the run, I will see:

time="2025-01-15T18:35:05Z" level=info msg="UPDATE-NEW: example.tld 0 IN TXT  \"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/redirs/example.tld\" []"
time="2025-01-15T18:35:05Z" level=info msg="UPDATE-NEW: a-example.tld 0 IN TXT  \"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/redirs/example.tld\" []"

At the end of the run, I also get a blob:

time="2025-01-15T18:35:05Z" level=warning msg="No matching zones were found for the following endpoints: [a-example.tld 0 IN TXT  \"heritage=external-dns,external-dns/owner=default,external-dns/resource=ingress/redirs/example.tld\"....

If I create the zone a-example.tld in PowerDNS the errors go away, but obviously I don't own a-example.tld.

I'm not sure why external-dns is prefixing all my domains with a- in addition to managing the domains without the a- prefix.

And honestly, it's not really the entire domain, it's just complaining about TXT records. It's like it's trying to create the heritage records in a prefixed zone. But the non-prefixed zones also have the proper text records.

What you expected to happen:
external-dns shouldn't be prefixing the domains for the text records with a-.

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

apiVersion: apps/v1
kind: Deployment
metadata:
  name: echo
spec:
  selector:
    matchLabels:
      app: echo
  template:
    metadata:
      labels:
        app: echo
    spec:
      containers:
      - image: hashicorp/http-echo
        name: echo
        ports:
        - containerPort: 5678
        args:
          - -text="Hello World"
---
apiVersion: v1
kind: Service
metadata:
  name: echo
  annotations:
    external-dns.alpha.kubernetes.io/hostname: echo.example.tld
spec:
  selector:
    app: echo
  type: LoadBalancer
  ports:
    - protocol: TCP
      port: 80
      targetPort: 5678

Environment:

• External-DNS version: 0.15.1
• DNS provider: PDNS

[ivankatliarchuk]

Hi darkpixel

Theres is a bit more about the a- prefixes #3757 (comment)

Related pull-reqests

1. feat(txt-registry): add option to use only new format #4946
2. fix(registry): only migrate from old to new records #4359

This design decision affects quite few of us, but may take a while to resolve

[darkpixel]

Thanks @ivankatliarchuk
Hopefully some of these PR's land soon.
I just made the dumb mistake of nuking all the heritage TXT records thinking some of them were hosed up.
Amazingly all the errors went away...until I tried to change an A record...because there's no heritage record anymore.

Oops.

Hopefully the migrate-txt-owner and the ability to forcibly take over a zone lands soon. I don't want to have to manually edit hundreds of domains. ;)