[bitnami/external-dns] Unable to Create a TXT Record for Apex/Root Domain

[Whooly27]

Name and Version

bitnami/external-dns 8.5.1

What architecture are you using?

amd64

What steps will reproduce the bug?

1. Set up external DNS with AWS provider
2. Attempt to create A and TXT records
3. Records for subdomains are properly created and tracked properly. Records for the apex domain must be deleted manually as they're not tracked due to the lack of the TXT record.

Are you using any custom parameters or values?

• '--metrics-address=:7979'
• '--log-level=debug'
• '--log-format=text'
• '--domain-filter=<APEX_DOMAIN>'
• '--policy=upsert-only'
• '--provider=aws'
• '--registry=txt'
• '--interval=1m'
• '--txt-owner-id=<HOSTED_ZONE_ID>'
• '--txt-prefix=externaldns.'
• '--source=istio-gateway'
• '--aws-api-retries=3'
• '--aws-zone-type=public'
• '--aws-batch-change-size=1000'
• '--txt-encrypt-enabled'
• '--txt-encrypt-aes-key=$(TXT_AES_ENCRYPTION_KEY)'

And the following values.yaml values:

valuesObject:
        txtPrefix: externaldns.
        logLevel: debug
        txtEncrypt:
          enabled: true
          secretName: txt-encrypt-secret
        txtOwnerId: {{ .Values.aws_route53_hosted_zone_id }}
        domainFilters:
          - <APEX_DOMAIN>
        provider: aws
        policy: upsert-only
        sources:
          - istio-gateway
        aws:
          zoneType: public
          credentials:
            accessKeyIDSecretRef:
              name: external-dns-secret
              key: access-key
            secretAccessKeySecretRef:
              name: external-dns-secret
              key: access-secret-key
          evaluateTargetHealth: true

What is the expected behavior?

TXT Records are created without the cname- prefix.

What do you see instead?

Skipping record {\n Action: \"CREATE\",\n ResourceRecordSet: {\n Name: \"externaldns.cname-<APEX_DOMAIN>\",\n ResourceRecords: [{\n Value: \"\\\".....\n }],\n TTL: 300,\n Type: \"TXT\"\n }\n} because no hosted zone matching record DNS Name was detected.

What is understandable as cname-APEX_DOMAIN doesn't exist, there's a hosted zone with the name of APEX_DOMAIN.

Meanwhile records for subdomains are added properly:
Adding externaldns.cname-www.APEX_DOMAIN to zone www.APEX_DOMAIN.

[javsalgar]

Hi,

Thank you for opening the ticket. It seems to me that this is not related to the Bitnami packaging of external-dns but with external-dns itself. Did you try reporting it to the upstream devs?

https://github.com/kubernetes-sigs/external-dns

[Whooly27]

Hi, thank you for your response. To track this issue in their repo, a ticket has been created.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.