Open
Description
What happened: My k8s ingress got redeployed and updated the application AWS ALB with a new URL. However, external-dns detected no change.
time="2025-03-13T10:35:06Z" level=info msg="Applying provider record filter for domains: [demo.mydomain.tech. .demo.mydomain.tech.]"
time="2025-03-13T10:35:06Z" level=info msg="All records are already up to date"
I manually deleted the stale A record from Route53, then external-dns picked it up:
│ time="2025-03-13T10:36:31Z" level=info msg="Applying provider record filter for domains: [demo.mydomain.tech. .demo.mydomain.tech.]" │
│ time="2025-03-13T10:36:31Z" level=info msg="Desired change: CREATE demo.mydomain.tech A [Id: /hostedzone/Z06779412XXXXXQW6TFKP]" │
│ time="2025-03-13T10:36:31Z" level=info msg="Desired change: CREATE demo.mydomain.tech TXT [Id: /hostedzone/Z06779412XXXXXQW6TFKP]" │
│ time="2025-03-13T10:36:31Z" level=info msg="2 record(s) in zone demo.mydomain.tech. [Id: /hostedzone/Z06779412XXXXXQW6TFKP] were successfully updated"
The A record is of ALIAS
type and routes back to the ALB URL.
What you expected to happen: external-dns detects the change, and performs the update.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- External-DNS version (use
external-dns --version
):external-dns external-dns 1 2025-02-24 14:14:52.714618 +0100 CET deployed external-dns-1.14.3 0.14.0
- DNS provider: Route53
- Others: