Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Heritage/Owner TXT record was not able to be created for DNSEndpoint of type TXT #4139

Closed
tanujd11 opened this issue Dec 27, 2023 · 0 comments · Fixed by #4140
Closed

Heritage/Owner TXT record was not able to be created for DNSEndpoint of type TXT #4139

tanujd11 opened this issue Dec 27, 2023 · 0 comments · Fixed by #4140
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@tanujd11
Copy link
Contributor

What happened:

I applied the following DNSEndpoint CR:

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
  name: random-txt-record
spec:
  endpoints:
    - dnsName: "random.example.com"
      recordType: "TXT"
      targets:
        - "random-text-value"
      recordTTL: 300

I had - --managed-record-types=TXT as one of the feature flags on the external DNS container. Now in my DNS zone I am able to see the record random.example.com being generated but it is orphan and no heritage TXT record is being generated. Note that txt-prefix is set in my case so that is not the issue.

What you expected to happen:
heritage/owner TXT record should also be created along with the TXT record

How to reproduce it (as minimally and precisely as possible):
Use the above DNSEndpoint CR to generate TXT record.

Anything else we need to know?:

Environment:

  • External-DNS version (use external-dns --version): v0.14.0
  • DNS provider: Azure Private DNS Zone
  • Others:
@tanujd11 tanujd11 added the kind/bug Categorizes issue or PR as related to a bug. label Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant