Unable to Create a TXT Record for Apex/Root Domain

[Whooly27]

Name and Version

Bitnami/external-dns 8.5.1 is packaged by Bitnami, but the issue lies with the external-dns package itself.

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.

[Lennie]

I believe the issue is probably a duplicate of #4234

[ivankatliarchuk]

/help
/area provider/aws

[k8s-ci-robot]

@ivankatliarchuk:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help
/area provider/aws

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-sigs/prow repository.