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

[bitnami/external-dns] Cloudflare A records not updated #4228

Closed
lucj opened this issue Feb 2, 2024 · 2 comments
Closed

[bitnami/external-dns] Cloudflare A records not updated #4228

lucj opened this issue Feb 2, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@lucj
Copy link

lucj commented Feb 2, 2024

What happened:

Cloudflare A records are not updated

What you expected to happen:

Cloudflare A record updated with the IP Address associated to the Ingress resource

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

I deployed external-dns with helm and provided the secret containing a cloudflare token.

The logs tell everything is up to date but the records are not updated

time="2024-02-02T16:36:42Z" level=info msg="All records are already up to date"

This is my ingress:

vote        vote   traefik   vote.mydomain.io,result.mydomain.io   89.XXX.YYY.ZZZ   80      16m

But in cloudflare the A record associated to vote.mydomain.com still have a previous value.

Anything else we need to know?:

I'm using Traefik ingress controler so traefik ingressClassName in my Ingress resource.

Environment:

  • External-DNS version (use external-dns --version): 0.14.0
  • DNS provider: Cloudflare
@lucj lucj added the kind/bug Categorizes issue or PR as related to a bug. label Feb 2, 2024
@lucj
Copy link
Author

lucj commented Feb 3, 2024

I changed the logLevel to debug and got some interesting things:

time="2024-02-03T10:59:01Z" level=debug msg="Skipping endpoint vote.mydomain.io 1 IN A  74.AAA.BBB.CCC [{external-dns.alpha.kubernetes.io/cloudflare-proxied true}] because owner id does not match, found: \"\", required: \"default\""

I set the txtOwnerId in my values file to "default" but this does not change anything. Below my current values.yaml

logLevel: debug
provider: cloudflare
cloudflare:
  secretName: cf-token
txtOwnerId: "default"

I probably messed things up on my side. Any hints what I must change ?
I don't really understand the purpose of the txtOwnerId field, should it be set with my domain name ?

Do I need to set a specify TXT record which indicates external-dns to be the owner of my domain for instance ?

@lucj
Copy link
Author

lucj commented Feb 3, 2024

I deleted the existing A records for my subdomains and I then saw they were recreated (along with TXT records, I guess those ones indicates external-dns owns these A records).

@lucj lucj closed this as completed Feb 3, 2024
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

No branches or pull requests

1 participant