Bug: Internet dropout skips update and never retries #553

New Issue

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

saavagebueno commented

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

Originally created by @davidlang42 on GitHub (Aug 19, 2025).

TLDR: When the internet connection drops out, the update gets skipped and never tried again until the next change.

Is this urgent: YES
DNS provider(s) you use: DuckDNS
Program version:

Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)

What are you using to run the container: TrueNAS "Apps" (aka TrueCharts)
Extra information: I've experienced this repeatedly, when the internet drops out, it fails to send an update, and then doesn't try again unless the container is stopped and restarted. What's worse, once I figured this out I saw in the logs that it only WARNS that it's doing this. It should probably be error? And also retry. The container crashing would even be better cause at least then I'd know there was a problem before I found myself unable to connect.

Logs:

2025-08-15 08:20:15.375777+00:002025-08-15T18:20:15+10:00 ERROR obtaining ipv4 or ipv6 address: after 3 tries, errors were: Get "https://api.seeip.org": context deadline exceeded, dial tcp: lookup dns.opendns.com: i/o timeout, Get "https://ip.changeip.com": context deadline exceeded
2025-08-15 08:20:15.375902+00:002025-08-15T18:20:15+10:00 WARN Skipping update for REDACTED.duckdns.org because IP address was not found

Configuration file:

{
  "settings": [
    {
      "domain": "duckdns.org",
      "ip_version": "",
      "provider": "duckdns",
      "token": "REDACTED"
    }
  ]
}

Host OS: TrueNAS Scale 24.20.2

Originally created by @davidlang42 on GitHub (Aug 19, 2025). **TLDR**: When the internet connection drops out, the update gets skipped and never tried again until the next change. 1. Is this urgent: YES 2. DNS provider(s) you use: DuckDNS 3. Program version: `Running version 2.9.0 built on 2024-12-24T10:40:42.120Z (commit 78f3061)` 4. What are you using to run the container: TrueNAS "Apps" (aka TrueCharts) 5. Extra information: I've experienced this repeatedly, when the internet drops out, it fails to send an update, and then doesn't try again unless the container is stopped and restarted. What's worse, once I figured this out I saw in the logs that it only WARNS that it's doing this. It should probably be error? And also retry. The container crashing would even be better cause at least then I'd know there was a problem before I found myself unable to connect. Logs: ```log 2025-08-15 08:20:15.375777+00:002025-08-15T18:20:15+10:00 ERROR obtaining ipv4 or ipv6 address: after 3 tries, errors were: Get "https://api.seeip.org": context deadline exceeded, dial tcp: lookup dns.opendns.com: i/o timeout, Get "https://ip.changeip.com": context deadline exceeded 2025-08-15 08:20:15.375902+00:002025-08-15T18:20:15+10:00 WARN Skipping update for REDACTED.duckdns.org because IP address was not found ``` Configuration file: ```json { "settings": [ { "domain": "duckdns.org", "ip_version": "", "provider": "duckdns", "token": "REDACTED" } ] } ``` Host OS: TrueNAS Scale 24.20.2

saavagebueno commented

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

@virtualdj commented on GitHub (Sep 23, 2025):

I would like a retry every xx minutes feature too, because it happens that the web UI shows "failure" but it does not retry and you're forced to kill the process (or the container) and restart it to update the DNS.

EDIT: I'm using Porkbun, so this is not related to the domain service.

@virtualdj commented on GitHub (Sep 23, 2025): I would like a _retry every xx minutes_ feature too, because it happens that the web UI shows "failure" but it does not retry and you're forced to kill the process (or the container) and restart it to update the DNS. EDIT: I'm using Porkbun, so this is not related to the domain service.

saavagebueno commented

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

@directhex commented on GitHub (Oct 3, 2025):

This plays havoc with my router's "reboot weekly just in case" default. Every Friday morning I find all my locally hosted services are inaccessible due to obsolete DNS

@directhex commented on GitHub (Oct 3, 2025): This plays havoc with my router's "reboot weekly just in case" default. Every Friday morning I find all my locally hosted services are inaccessible due to obsolete DNS

saavagebueno commented

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

@granjerox commented on GitHub (Oct 12, 2025):

For me, it has been running fine since July.
But I had to restart ddns-updater service this morning to force recheck and update after last night update error:

2025-10-09T05:01:33+02:00 ERROR obtaining ipv4 address: after 3 tries, errors were: Get "https://v4.ident.me": context deadline exceeded, dial tcp4 1.1.1.1:853: i/o timeout, Get "https://ip4.nnev.de": context deadline exceeded
2025-10-09T05:01:33+02:00 WARN Skipping update for XXXXXX.ovh because ipv4 address was not found
2025-10-09T05:01:33+02:00 WARN Skipping update for any.XXXXXX.ovh because ipv4 address was not found

{
  "provider": "ovh",
  "mode": "api",
  "domain": "XXXXXXXXXXXXXX.ovh",
  "api_endpoint": "ovh-eu",
  "app_key": "XXXXXXXXXXXXXX",
  "app_secret": "XXXXXXXXXXXXXX",
  "consumer_key": "XXXXXXXXXXXXXX",
  "ip_version": "ipv4",
  "ipv6_suffix": ""
},

Docker container running under UNRAID
Running version latest built on 2025-10-07T16:30:09.195Z (commit 95bcce2)

@granjerox commented on GitHub (Oct 12, 2025): For me, it has been running fine since July. But I had to restart ddns-updater service this morning to force recheck and update after last night update error: ```log 2025-10-09T05:01:33+02:00 ERROR obtaining ipv4 address: after 3 tries, errors were: Get "https://v4.ident.me": context deadline exceeded, dial tcp4 1.1.1.1:853: i/o timeout, Get "https://ip4.nnev.de": context deadline exceeded 2025-10-09T05:01:33+02:00 WARN Skipping update for XXXXXX.ovh because ipv4 address was not found 2025-10-09T05:01:33+02:00 WARN Skipping update for any.XXXXXX.ovh because ipv4 address was not found ``` ```json { "provider": "ovh", "mode": "api", "domain": "XXXXXXXXXXXXXX.ovh", "api_endpoint": "ovh-eu", "app_key": "XXXXXXXXXXXXXX", "app_secret": "XXXXXXXXXXXXXX", "consumer_key": "XXXXXXXXXXXXXX", "ip_version": "ipv4", "ipv6_suffix": "" }, ``` ``` Docker container running under UNRAID Running version latest built on 2025-10-07T16:30:09.195Z (commit 95bcce2) ```

saavagebueno commented

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

@directhex commented on GitHub (Oct 17, 2025):

This plays havoc with my router's "reboot weekly just in case" default. Every Friday morning I find all my locally hosted services are inaccessible due to obsolete DNS

Why yes it's Friday morning and I'm back on here, how can you tell?. Dumb mitigation proposed.

@directhex commented on GitHub (Oct 17, 2025): > This plays havoc with my router's "reboot weekly just in case" default. Every Friday morning I find all my locally hosted services are inaccessible due to obsolete DNS Why yes it's Friday morning and I'm back on here, how can you tell?. Dumb mitigation proposed.

saavagebueno commented

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

@tadeusz-niemiec commented on GitHub (Oct 20, 2025):

Bump, this is crucial, I've just found myself unable to connect to my homelab. Since proper DNS records are required even for VPNs to work, whenever this bug occurs I'm stuck and can't fix it remotely

@tadeusz-niemiec commented on GitHub (Oct 20, 2025): Bump, this is crucial, I've just found myself unable to connect to my homelab. Since proper DNS records are required even for VPNs to work, whenever this bug occurs I'm stuck and can't fix it remotely

saavagebueno commented

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

@mamoep commented on GitHub (Nov 10, 2025):

+1

@mamoep commented on GitHub (Nov 10, 2025): +1

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#553