Bug: The updater was flopping between by correct WAN IP and possibly an older one that was not correct #207

New Issue

saavagebueno · 2025-11-20T04:21:32-05:00

saavagebueno commented

2025-11-20 04:21:32 -05:00

Originally created by @sarg3nt on GitHub (Aug 16, 2022).

Originally assigned to: @qdm12 on GitHub.

Is this urgent: Maybe?
DNS provider(s) you use: Cloudflare
Program version: Running version latest built on 2022-03-15T14:38:50Z (commit 584597d)
What are you using to run the container: Unraid

My config:

{
  "settings": [
    {
      "provider": "cloudflare",
      "zone_identifier": "<redacted>",
      "domain": "sarge.info",
      "host": "@",
      "ttl": 600,
      "token": "<redacted>",
      "ip_version": "ipv4"
    },
    {
      "provider": "cloudflare",
      "zone_identifier": "<redacted>",
      "domain": "sarge.systems",
      "host": "@",
      "ttl": 600,
      "token": "<redacted>",
      "ip_version": "ipv4"
    }
  ]
}

Detail:

DDNS updater was constantly changing my IP registration with Cloudflare from the correct current WAN IP to an invalid (maybe older one?), then back to the correct one and back again to the old one, constantly flip flopping them.
At lease one of the http sources is no longer working and I have no idea how the DNS sources are supposed to know what my current IP is, that doesn't make sense to me.
I edited the config and set PUBLICIP_FETCHERS=http (no dns) and PUBLICIP_HTTP_PROVIDERS=ifconfig,ipinfo,google and that fixed it.

Items that need fixed / improved:

The docs don't go into how the DNS PUBLICIP_FETCHERS are supposed to work. I don't get it and as part of the troubleshooting I set it to http only and I think that was part or all of the fix.
The opendns entry which maps to https://diagnostic.opendns.com/myip according to your docs, no longer works
The container throws errors if ddnss is included. in PUBLICIP_HTTP_PROVIDERS

Originally created by @sarg3nt on GitHub (Aug 16, 2022). Originally assigned to: @qdm12 on GitHub. 1. Is this urgent: Maybe? 2. DNS provider(s) you use: Cloudflare 3. Program version: Running version latest built on 2022-03-15T14:38:50Z (commit 584597d) 4. What are you using to run the container: Unraid My config: ```json { "settings": [ { "provider": "cloudflare", "zone_identifier": "<redacted>", "domain": "sarge.info", "host": "@", "ttl": 600, "token": "<redacted>", "ip_version": "ipv4" }, { "provider": "cloudflare", "zone_identifier": "<redacted>", "domain": "sarge.systems", "host": "@", "ttl": 600, "token": "<redacted>", "ip_version": "ipv4" } ] } ``` **Detail:** DDNS updater was constantly changing my IP registration with Cloudflare from the correct current WAN IP to an invalid (maybe older one?), then back to the correct one and back again to the old one, constantly flip flopping them. At lease one of the http sources is no longer working and I have no idea how the DNS sources are supposed to know what my current IP is, that doesn't make sense to me. I edited the config and set `PUBLICIP_FETCHERS=http` (no dns) and `PUBLICIP_HTTP_PROVIDERS=ifconfig,ipinfo,google` and that fixed it. **Items that need fixed / improved:** 1. The docs don't go into how the DNS `PUBLICIP_FETCHERS` are supposed to work. I don't get it and as part of the troubleshooting I set it to `http` only and I think that was part or all of the fix. 2. The `opendns` entry which maps to `https://diagnostic.opendns.com/myip` according to your docs, no longer works 3. The container throws errors if `ddnss` is included. in `PUBLICIP_HTTP_PROVIDERS`

saavagebueno added the Status: 🗯️ Waiting for feedback Closed: ⚰️ Inactive labels 2025-11-20 04:21:32 -05:00

saavagebueno closed this issue

2025-11-20 04:21:32 -05:00

saavagebueno commented

2025-11-20 04:21:32 -05:00

@Bcjc3 commented on GitHub (Mar 25, 2023):

I stumble through all the same steps you did, then found your post here. I had the same issue, found the same opendns problem in the documentation, swapped PUBLICIP_FETCHERS and PUBLICIP_HTTP_PROVIDERS to the same settings. I am hoping it is still fixed for you, because it seems I am following in your same steps. I don't know where the other rouge IP addresses came from, but I can tell you it was not any of my previous ones. I filled a log full of +875 entries of swapping back and forth between some random addresses that I still don't know where they came from. I am going to keep an eye on mine to make sure I don't get the wrong IP address again.

@Bcjc3 commented on GitHub (Mar 25, 2023): I stumble through all the same steps you did, then found your post here. I had the same issue, found the same opendns problem in the documentation, swapped PUBLICIP_FETCHERS and PUBLICIP_HTTP_PROVIDERS to the same settings. I am hoping it is still fixed for you, because it seems I am following in your same steps. I don't know where the other rouge IP addresses came from, but I can tell you it was not any of my previous ones. I filled a log full of +875 entries of swapping back and forth between some random addresses that I still don't know where they came from. I am going to keep an eye on mine to make sure I don't get the wrong IP address again.

saavagebueno commented

2025-11-20 04:21:32 -05:00

@ajw107 commented on GitHub (Apr 29, 2023):

Don't know how helpful this is, but I also have this issue. I also noted the erroneous ip increments (i.e. goes from x.y.x.236 then x.y.z.237, etc) and I get some ipv6 addresses in there too, even though I have it set to ipv4 only.. I'm going to try without the dns method, as in here and see if this helps.
EDIT: Forgot to mention my provider is Gandi (as the others are Cloudflare) and I'm running it in a docker

@ajw107 commented on GitHub (Apr 29, 2023): Don't know how helpful this is, but I also have this issue. I also noted the erroneous ip increments (i.e. goes from x.y.x.236 then x.y.z.237, etc) and I get some ipv6 addresses in there too, even though I have it set to ipv4 only.. I'm going to try without the dns method, as in here and see if this helps. EDIT: Forgot to mention my provider is Gandi (as the others are Cloudflare) and I'm running it in a docker

saavagebueno commented

2025-11-20 04:21:33 -05:00

@Bcjc3 commented on GitHub (May 5, 2023):

After a month of my previous modification, I can say it is working great! It hasn't changed to any other IP addresses, and all is looking good!

@Bcjc3 commented on GitHub (May 5, 2023): After a month of my previous modification, I can say it is working great! It hasn't changed to any other IP addresses, and all is looking good!

saavagebueno commented

2025-11-20 04:21:33 -05:00

@qdm12 commented on GitHub (Jun 13, 2023):

sorry for the mega delay -

DDNS updater was constantly changing my IP registration with Cloudflare from the correct current WAN IP to an invalid (maybe older one?), then back to the correct one and back again to the old one, constantly flip flopping them.

If it still is failing, run it with LOG_LEVEL=debug you should get more information on where the program fishes out public ip information etc.

At lease one of the http sources is no longer working and I have no idea how the DNS sources are supposed to know what my current IP is, that doesn't make sense to me.

It's special DNS queries just to get your ip back, nothing to do with your domain name provider really 😉

For example:

docker run -it --rm alpine:3.18 sh -c "apk add bind-tools && dig +short @ns1.google.com -t txt o-o.myaddr.l.google.com"

BTW side note, I just added the opendns option along the google and cloudflare options for DNS ip fetchers, in c12b7e50d7

2. The opendns entry which maps to https://diagnostic.opendns.com/myip according to your docs, no longer works

It is out from now on! Done in baacd052ce

3. The container throws errors if ddnss is included. in PUBLICIP_HTTP_PROVIDERS

Digging through dusty git commits, it was removed in 5557c32135 because it was geo-blocking some users. I just removed it from the readme (looks like it didn't get removed properly) in feaac82c11

@sarg3nt @ajw107 I suggest you try with the latest image, it might just work due to a few recent changes.

@qdm12 commented on GitHub (Jun 13, 2023): - sorry for the mega delay - > DDNS updater was constantly changing my IP registration with Cloudflare from the correct current WAN IP to an invalid (maybe older one?), then back to the correct one and back again to the old one, constantly flip flopping them. If it still is failing, run it with `LOG_LEVEL=debug` you should get more information on where the program fishes out public ip information etc. > At lease one of the http sources is no longer working and I have no idea how the DNS sources are supposed to know what my current IP is, that doesn't make sense to me. It's special DNS queries just to get your ip back, nothing to do with your domain name provider really 😉 For example: ```sh docker run -it --rm alpine:3.18 sh -c "apk add bind-tools && dig +short @ns1.google.com -t txt o-o.myaddr.l.google.com" ``` BTW side note, I just added the `opendns` option along the `google` and `cloudflare` options for DNS ip fetchers, in c12b7e50d7999224b4790ffd44ba985202c8f454 > 2\. The `opendns` entry which maps to `https://diagnostic.opendns.com/myip` according to your docs, no longer works It is out from now on! Done in baacd052ce25690912282502fc3433bb43618c89 > 3\. The container throws errors if `ddnss` is included. in `PUBLICIP_HTTP_PROVIDERS` Digging through dusty git commits, it was removed in 5557c321351283d8a7f7ac83f9a9d9252c10a4e8 because it was geo-blocking some users. I just removed it from the readme (looks like it didn't get removed properly) in feaac82c11b8fefb1382ee8978cd53bfea350e99 @sarg3nt @ajw107 I suggest you try with the latest image, it might *just work* due to a few recent changes.

saavagebueno commented

2025-11-20 04:21:33 -05:00

@qdm12 commented on GitHub (Jan 19, 2024):

Closing due to inactivity, feel free to comment and I'll re-open.

@qdm12 commented on GitHub (Jan 19, 2024): Closing due to inactivity, feel free to comment and I'll re-open.

saavagebueno referenced this issue

2025-11-20 04:25:35 -05:00

[PR #207] [MERGED] Feature: DD24 support #652

Sign in to join this conversation.