Bug: IP address constantly "updated" #505

New Issue

saavagebueno · 2025-11-20T04:24:36-05:00

saavagebueno commented

2025-11-20 04:24:36 -05:00

Originally created by @hazzabeee on GitHub (Mar 7, 2025).

TLDR: IP address constantly "updates" even though it hasn't changed.

This causes log spam (and 600+ "previous IPs", all identical).

Is this urgent: No
DNS provider(s) you use: Cloudlfare
Program version:

Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061)
What are you using to run the container: docker-compose
Extra information (optional)

Logs:

Host OS: Debian

Originally created by @hazzabeee on GitHub (Mar 7, 2025).  **TLDR**: IP address constantly "updates" even though it hasn't changed. This causes log spam (and 600+ "previous IPs", all identical). 1. Is this urgent: No 2. DNS provider(s) you use: Cloudlfare 3. Program version:  `Running version latest built on 2024-12-24T09:20:36.130Z (commit 78f3061)` 4. What are you using to run the container: docker-compose 5. Extra information (optional) Logs: ```INFO Updating record [domain: mydomain.co.uk | owner: www | provider: ionos | ip: ipv4] to use IP_ADDRESS ``` Host OS: Debian

saavagebueno commented

2025-11-20 04:24:37 -05:00

@thomasZ74 commented on GitHub (Mar 18, 2025):

Hi,
I've noticed this issue as well. My IP is also updated on each iteration, even though it hasn't changed.
I think the problem is not only with the logs, but it also causes constant requests to the provider (risk of a ban?).

@thomasZ74 commented on GitHub (Mar 18, 2025): Hi, I've noticed this issue as well. My IP is also updated on each iteration, even though it hasn't changed. I think the problem is not only with the logs, but it also causes constant requests to the provider (risk of a ban?).

saavagebueno commented

2025-11-20 04:24:37 -05:00

@klofrau commented on GitHub (Mar 19, 2025):

edit: Nevermind. It was an issue with dns. Tailscale messed with my resolv.conf. This way ddns-updater couldn't resolve my domain's ip address.
Solved by setting RESOLVER_ADDRESS to a pulic dns server.

~~Same for me. Logs look like this:~~

~~<timestamps> INFO ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:fff:2400:be24:11ff:fd09:1faf~~
~~<timestamps> INFO Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:fff:2400:be24:11ff:fe09:1faf~~

~~<timestamps> INFO ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:f3de:200:be24:11ff:fd09:1faf~~
~~<timestamps> Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:f3de:200:be24:11ff:fd09:1faf~~

~~<timestamps> ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:f3de:200:be24:11ff:fd09:1faf~~
~~<timestamps> INFO Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:f3de:200:be24:11ff:fd09:1faf~~

~~You can see the empty address there as well. Also the dns-providers api log shows an actual update to the entry, even though the address has not actually changed~~

@klofrau commented on GitHub (Mar 19, 2025): edit: Nevermind. It was an issue with dns. Tailscale messed with my resolv.conf. This way ddns-updater couldn't resolve my domain's ip address. Solved by setting RESOLVER_ADDRESS to a pulic dns server. ~~Same for me. Logs look like this:~~ ~~`<timestamps> INFO ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:fff:2400:be24:11ff:fd09:1faf`~~ ~~`<timestamps> INFO Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:fff:2400:be24:11ff:fe09:1faf`~~ ~~`<timestamps> INFO ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:f3de:200:be24:11ff:fd09:1faf`~~ ~~`<timestamps> Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:f3de:200:be24:11ff:fd09:1faf`~~ ~~`<timestamps> ipv6 address of my.domain.example is and your ipv6 address is 2c02:d30:f3de:200:be24:11ff:fd09:1faf`~~ ~~`<timestamps> INFO Updating record [domain: domain.example | owner: my | provider: netcup | ip: ipv6] to use 2c02:d30:f3de:200:be24:11ff:fd09:1faf`~~ ~~You can see the empty address there as well. Also the dns-providers api log shows an actual update to the entry, even though the address has not actually changed~~

saavagebueno commented

2025-11-20 04:24:37 -05:00

@danutzzzzz commented on GitHub (May 18, 2025):

Hi have the same issue but only on the root domain, im already using an external dns resolver..

@danutzzzzz commented on GitHub (May 18, 2025): Hi have the same issue but only on the root domain, im already using an external dns resolver.. ![Image](https://github.com/user-attachments/assets/1326a9d6-d650-48e3-825f-7a9d746012c4)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#505