starred/ddns-updater
1
0
Fork 0
mirror of https://github.com/qdm12/ddns-updater.git synced 2026-06-04 14:21:55 -04:00
Code Issues 312 Packages Projects Releases 10 Wiki Activity

Bug: IPv6 doesn't always include last 4 parts. #209

New Issue
Closed
opened 2025-11-20 04:21:33 -05:00 by saavagebueno · 9 comments
saavagebueno commented 2025-11-20 04:21:33 -05:00
Owner
Copy Link

Originally created by @charlesomer on GitHub (Aug 27, 2022).

Originally assigned to: @qdm12 on GitHub.

TLDR: IPv6 address sometimes gets set without the last 4 parts.

  1. Is this urgent: Yes

  2. DNS provider(s) you use: Digital Ocean

  3. Program version: Running version latest built on 2022-03-15T14:38:50Z (commit 584597d)

    Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)

  4. What are you using to run the container: docker-compose

  5. Extra information (optional): I have tried with both /64 and /128. I can't see a way to exec into the container to test the curls but they work fine from the host. Apologies if I've missed something obvious. It's odd to me that it will sometimes work correctly.

Logs:
Due to restarting the container I don't have the logs at the moment.

Configuration file (remove your credentials!):

  ddns-updater:
    image: qmcgaw/ddns-updater
    container_name: ddns-updater
    network_mode: bridge
    ports:
      - 8000:8000/tcp
    environment:
      - CONFIG={"settings":[{"provider":"digitalocean","domain":"[removed]","host":"[removed]","token":"[removed]","ip_version":"ipv6"}]}
      - BACKUP_PERIOD=72h # 0 to disable
      - TZ=Europe/London
    restart: always
    logging:
      options:
        max-size: "200k"
        max-file: "10"

Host OS:
Raspberry Pi OS 32 bit

Originally created by @charlesomer on GitHub (Aug 27, 2022). Originally assigned to: @qdm12 on GitHub. <!-- YOU CAN CHAT THERE EVENTUALLY: https://github.com/qdm12/ddns-updater/discussions --> **TLDR**: IPv6 address sometimes gets set without the last 4 parts. 1. Is this urgent: Yes 2. DNS provider(s) you use: Digital Ocean 3. Program version: Running version latest built on 2022-03-15T14:38:50Z (commit 584597d) <!-- See the line at the top of your logs --> `Running version latest built on 2020-03-13T01:30:06Z (commit d0f678c)` 4. What are you using to run the container: docker-compose 5. Extra information (optional): I have tried with both /64 and /128. I can't see a way to exec into the container to test the curls but they work fine from the host. Apologies if I've missed something obvious. It's odd to me that it will sometimes work correctly. Logs: Due to restarting the container I don't have the logs at the moment. Configuration file (**remove your credentials!**): ```json ddns-updater: image: qmcgaw/ddns-updater container_name: ddns-updater network_mode: bridge ports: - 8000:8000/tcp environment: - CONFIG={"settings":[{"provider":"digitalocean","domain":"[removed]","host":"[removed]","token":"[removed]","ip_version":"ipv6"}]} - BACKUP_PERIOD=72h # 0 to disable - TZ=Europe/London restart: always logging: options: max-size: "200k" max-file: "10" ``` Host OS: Raspberry Pi OS 32 bit
saavagebueno commented 2025-11-20 04:21:34 -05:00
Author
Owner
Copy Link

@edaubert commented on GitHub (Jan 11, 2023):

I had the same issue but specifying IPV6_PREFIX=/128 seems to have fix it

@edaubert commented on GitHub (Jan 11, 2023): I had the same issue but specifying `IPV6_PREFIX=/128` seems to have fix it
saavagebueno commented 2025-11-20 04:21:34 -05:00
Author
Owner
Copy Link

@tom-a-wagner commented on GitHub (May 4, 2023):

I have the same issue. Setting IPV6_PREFIX=/128 explicitely doesn't help.

However, I found that the issue only happens when using http as a public ip fetcher, while I get the correct ip when using dns, but then another error.

I manually specified a single site so I can query it manually to compare, it returned (redacted) aaaa:bbbb:cccc:dddd::d89.

The http method however just determines aaaa:bbbb:cccc:dddd:: as my address:

podman run --privileged --name ddns-updater -e 'LOG_LEVEL=debug' -e 'IPV6_PREFIX=/128' -e 'PUBLICIP_FETCHERS=http' -e 'PUBLICIPV6_HTTP_PROVIDERS=https://api6.ipify.org/' -p 8000:8000 -v "$PWD:/updater/data" ghcr.io/qdm12/ddns-updater
========================================
========================================
============= ddns-updater =============
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================

Running version latest built on 2023-05-03T11:04:31Z (commit 28509cf)

🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new
🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new
✨ New feature? https://github.com/qdm12/ddns-updater/issues/new
☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new
💻 Email? quentin.mcgaw@gmail.com
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2023-05-04T12:38:04Z INFO reading JSON config from file /updater/data/config.json
2023-05-04T12:38:04Z DEBUG config read: {
    "settings": [
      {
        "provider": "google",
        "domain": "<redacted>",
        "host": "<redacted>",
        "username": "<redacted>",
        "password": "<redacted>",
        "ip_version": "ipv6"
      }
    ]
  }
2023-05-04T12:38:04Z INFO Found single setting to update record
2023-05-04T12:38:04Z INFO Reading history from database: domain <redacted> host <redacted>
2023-05-04T12:38:04Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: true
2023-05-04T12:38:04Z INFO [healthcheck server] listening on 127.0.0.1:9999
2023-05-04T12:38:04Z INFO [http server] listening on :8000
2023-05-04T12:38:04Z INFO [backup] disabled
2023-05-04T12:38:05Z DEBUG your public IP address are: v4 or v6: <nil>, v4: <nil>, v6: aaaa:bbbb:cccc:dddd::
2023-05-04T12:38:05Z DEBUG IPv6 address of <redacted> is aaaa:bbbb:cccc:dddd:: and your IPv6 address is aaaa:bbbb:cccc:dddd::, skipping update

When using dns instead, this happens:

podman run --privileged --name ddns-updater -e 'LOG_LEVEL=debug' -e 'IPV6_PREFIX=/128' -e 'PUBLICIP_FETCHERS=dns' -p 8000:8000 -v "$PWD:/updater/data" ghcr.io/qdm12/ddns-updater
========================================
========================================
============= ddns-updater =============
========================================
=========== Made with ❤️ by ============
======= https://github.com/qdm12 =======
========================================
========================================

Running version latest built on 2023-05-03T11:04:31Z (commit 28509cf)

🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new
🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new
✨ New feature? https://github.com/qdm12/ddns-updater/issues/new
☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new
💻 Email? quentin.mcgaw@gmail.com
💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12
2023-05-04T12:47:12Z INFO reading JSON config from file /updater/data/config.json
2023-05-04T12:47:12Z DEBUG config read: {
    "settings": [
      {
        "provider": "google",
        "domain": "<redacted>",
        "host": "<redacted>",
        "username": "<redacted>",
        "password": "<redacted>",
        "ip_version": "ipv6"
      }
    ]
  }
2023-05-04T12:47:12Z INFO Found single setting to update record
2023-05-04T12:47:12Z INFO Reading history from database: domain <redacted> host <redacted>
2023-05-04T12:47:12Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: true
2023-05-04T12:47:12Z INFO [backup] disabled
2023-05-04T12:47:12Z INFO [healthcheck server] listening on 127.0.0.1:9999
2023-05-04T12:47:12Z INFO [http server] listening on :8000
2023-05-04T12:47:12Z DEBUG your public IP address are: v4 or v6: <nil>, v4: <nil>, v6: aaaa:bbbb:cccc:dddd::d89
2023-05-04T12:47:12Z INFO IPv6 address of <redacted>.<redacted> is aaaa:bbbb:cccc:dddd:: and your IPv6 address is aaaa:bbbb:cccc:dddd::d89
2023-05-04T12:47:12Z INFO Updating record [domain: <redacted> | host: <redacted> | provider: google | ip: ipv6] to use aaaa:bbbb:cccc:dddd::d89
2023-05-04T12:47:12Z DEBUG GET https://<redacted>:<redacted>@domains.google.com/nic/update?hostname=<redacted>.<redacted>&myip=aaaa%3Abbbb%3Acccc%3Adddd%3A%3Ad89 | headers: Authorization: Basic <redacted>; User-Agent: DDNS-Updater quentin.mcgaw@gmail.com
2023-05-04T12:47:13Z DEBUG 200 OK | headers: Cross-Origin-Opener-Policy: same-origin; Cross-Origin-Resource-Policy: same-site; Server: ESF; Date: Thu, 04 May 2023 12:47:13 GMT; Vary: Sec-Fetch-Dest, Sec-Fetch-Mode, Sec-Fetch-Site; P3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."; Permissions-Policy: ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-platform=*, ch-ua-platform-version=*; Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000; Content-Type: text/html; charset=utf-8; Content-Security-Policy: require-trusted-types-for 'script';report-uri /_/DomainsDynamicDns/cspreport,script-src 'report-sample' 'nonce-uhT1tk49FdqWSzYrr9H73A' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/DomainsDynamicDns/cspreport;worker-src 'self'; X-Frame-Options: SAMEORIGIN; X-Content-Type-Options: nosniff; Set-Cookie: <redacted>; expires=Fri, 03-Nov-2023 12:47:12 GMT; path=/; domain=.google.com; HttpOnly; Strict-Transport-Security: max-age=31536000; Pragma: no-cache; Expires: Mon, 01 Jan 1990 00:00:00 GMT; Accept-Ch: Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Full-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Model, Sec-CH-UA-WoW64, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version; X-Xss-Protection: 0; Cache-Control: no-cache, no-store, max-age=0, must-revalidate | body: good aaaa:bbbb:cccc:dddd::d89
2023-05-04T12:47:13Z ERROR mismatching IP address received: aaaa:bbbb:cccc:dddd::

The IP is determined and updated correctly, but then i get mismatching IP address received: aaaa:bbbb:cccc:dddd:: with the incorrect IP, not sure what that error means.

@tom-a-wagner commented on GitHub (May 4, 2023): I have the same issue. Setting `IPV6_PREFIX=/128` explicitely doesn't help. However, I found that the issue only happens when using http as a public ip fetcher, while I get the correct ip when using dns, but then another error. I manually specified a single site so I can query it manually to compare, it returned (redacted) `aaaa:bbbb:cccc:dddd::d89`. The http method however just determines `aaaa:bbbb:cccc:dddd::` as my address: ``` podman run --privileged --name ddns-updater -e 'LOG_LEVEL=debug' -e 'IPV6_PREFIX=/128' -e 'PUBLICIP_FETCHERS=http' -e 'PUBLICIPV6_HTTP_PROVIDERS=https://api6.ipify.org/' -p 8000:8000 -v "$PWD:/updater/data" ghcr.io/qdm12/ddns-updater ======================================== ======================================== ============= ddns-updater ============= ======================================== =========== Made with ❤️ by ============ ======= https://github.com/qdm12 ======= ======================================== ======================================== Running version latest built on 2023-05-03T11:04:31Z (commit 28509cf) 🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new 🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new 💻 Email? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2023-05-04T12:38:04Z INFO reading JSON config from file /updater/data/config.json 2023-05-04T12:38:04Z DEBUG config read: { "settings": [ { "provider": "google", "domain": "<redacted>", "host": "<redacted>", "username": "<redacted>", "password": "<redacted>", "ip_version": "ipv6" } ] } 2023-05-04T12:38:04Z INFO Found single setting to update record 2023-05-04T12:38:04Z INFO Reading history from database: domain <redacted> host <redacted> 2023-05-04T12:38:04Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: true 2023-05-04T12:38:04Z INFO [healthcheck server] listening on 127.0.0.1:9999 2023-05-04T12:38:04Z INFO [http server] listening on :8000 2023-05-04T12:38:04Z INFO [backup] disabled 2023-05-04T12:38:05Z DEBUG your public IP address are: v4 or v6: <nil>, v4: <nil>, v6: aaaa:bbbb:cccc:dddd:: 2023-05-04T12:38:05Z DEBUG IPv6 address of <redacted> is aaaa:bbbb:cccc:dddd:: and your IPv6 address is aaaa:bbbb:cccc:dddd::, skipping update ``` When using dns instead, this happens: ``` podman run --privileged --name ddns-updater -e 'LOG_LEVEL=debug' -e 'IPV6_PREFIX=/128' -e 'PUBLICIP_FETCHERS=dns' -p 8000:8000 -v "$PWD:/updater/data" ghcr.io/qdm12/ddns-updater ======================================== ======================================== ============= ddns-updater ============= ======================================== =========== Made with ❤️ by ============ ======= https://github.com/qdm12 ======= ======================================== ======================================== Running version latest built on 2023-05-03T11:04:31Z (commit 28509cf) 🔧 Need help? https://github.com/qdm12/ddns-updater/discussions/new 🐛 Bug? https://github.com/qdm12/ddns-updater/issues/new ✨ New feature? https://github.com/qdm12/ddns-updater/issues/new ☕ Discussion? https://github.com/qdm12/ddns-updater/discussions/new 💻 Email? quentin.mcgaw@gmail.com 💰 Help me? https://www.paypal.me/qmcgaw https://github.com/sponsors/qdm12 2023-05-04T12:47:12Z INFO reading JSON config from file /updater/data/config.json 2023-05-04T12:47:12Z DEBUG config read: { "settings": [ { "provider": "google", "domain": "<redacted>", "host": "<redacted>", "username": "<redacted>", "password": "<redacted>", "ip_version": "ipv6" } ] } 2023-05-04T12:47:12Z INFO Found single setting to update record 2023-05-04T12:47:12Z INFO Reading history from database: domain <redacted> host <redacted> 2023-05-04T12:47:12Z DEBUG configured to fetch IP: v4 or v6: false, v4: false, v6: true 2023-05-04T12:47:12Z INFO [backup] disabled 2023-05-04T12:47:12Z INFO [healthcheck server] listening on 127.0.0.1:9999 2023-05-04T12:47:12Z INFO [http server] listening on :8000 2023-05-04T12:47:12Z DEBUG your public IP address are: v4 or v6: <nil>, v4: <nil>, v6: aaaa:bbbb:cccc:dddd::d89 2023-05-04T12:47:12Z INFO IPv6 address of <redacted>.<redacted> is aaaa:bbbb:cccc:dddd:: and your IPv6 address is aaaa:bbbb:cccc:dddd::d89 2023-05-04T12:47:12Z INFO Updating record [domain: <redacted> | host: <redacted> | provider: google | ip: ipv6] to use aaaa:bbbb:cccc:dddd::d89 2023-05-04T12:47:12Z DEBUG GET https://<redacted>:<redacted>@domains.google.com/nic/update?hostname=<redacted>.<redacted>&myip=aaaa%3Abbbb%3Acccc%3Adddd%3A%3Ad89 | headers: Authorization: Basic <redacted>; User-Agent: DDNS-Updater quentin.mcgaw@gmail.com 2023-05-04T12:47:13Z DEBUG 200 OK | headers: Cross-Origin-Opener-Policy: same-origin; Cross-Origin-Resource-Policy: same-site; Server: ESF; Date: Thu, 04 May 2023 12:47:13 GMT; Vary: Sec-Fetch-Dest, Sec-Fetch-Mode, Sec-Fetch-Site; P3p: CP="This is not a P3P policy! See g.co/p3phelp for more info."; Permissions-Policy: ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-platform=*, ch-ua-platform-version=*; Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000; Content-Type: text/html; charset=utf-8; Content-Security-Policy: require-trusted-types-for 'script';report-uri /_/DomainsDynamicDns/cspreport,script-src 'report-sample' 'nonce-uhT1tk49FdqWSzYrr9H73A' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /_/DomainsDynamicDns/cspreport;worker-src 'self'; X-Frame-Options: SAMEORIGIN; X-Content-Type-Options: nosniff; Set-Cookie: <redacted>; expires=Fri, 03-Nov-2023 12:47:12 GMT; path=/; domain=.google.com; HttpOnly; Strict-Transport-Security: max-age=31536000; Pragma: no-cache; Expires: Mon, 01 Jan 1990 00:00:00 GMT; Accept-Ch: Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Full-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Model, Sec-CH-UA-WoW64, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version; X-Xss-Protection: 0; Cache-Control: no-cache, no-store, max-age=0, must-revalidate | body: good aaaa:bbbb:cccc:dddd::d89 2023-05-04T12:47:13Z ERROR mismatching IP address received: aaaa:bbbb:cccc:dddd:: ``` The IP is determined and updated correctly, but then i get `mismatching IP address received: aaaa:bbbb:cccc:dddd::` with the incorrect IP, not sure what that error means.
saavagebueno commented 2025-11-20 04:21:34 -05:00
Author
Owner
Copy Link

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

Please pull the latest image and try again. A lot of work has been going on recently to use net/netip ip addresses and some changes were made regarding the masking for ipv6, so maybe it will help. Error messages should now be clearer too regarding the mismatching IP address received thing.

For google, it happens in the code here:

936bf4386e/internal/settings/providers/google/provider.go (L166)

So the ip you get from the response is different from the ip sent out to update your record with, most likely due to that ipv6 prefix mask I guess?

@qdm12 commented on GitHub (Jun 12, 2023): Please pull the latest image and try again. A lot of work has been going on recently to use `net/netip` ip addresses and some changes were made regarding the masking for ipv6, so maybe it will help. Error messages should now be clearer too regarding the mismatching IP address received thing. For google, it happens in the code here: https://github.com/qdm12/ddns-updater/blob/936bf4386e26f9c22105e62f5d357bdaf66af5c3/internal/settings/providers/google/provider.go#L166 So the ip you get from the response is different from the ip sent out to update your record with, most likely due to that ipv6 prefix mask I guess?
saavagebueno commented 2025-11-20 04:21:34 -05:00
Author
Owner
Copy Link

@tom-a-wagner commented on GitHub (Jun 12, 2023):

Just tested again with commit 5676673.

No change, except that setting PUBLICIP_FETCHERS=dns now results in the same output as setting http.

The address is still printed with the last part missing:

2023-06-12T15:56:58Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: invalid IP, v6: aaaa:bbbb:cccc:dddd::
@tom-a-wagner commented on GitHub (Jun 12, 2023): Just tested again with commit 5676673. No change, except that setting `PUBLICIP_FETCHERS=dns` now results in the same output as setting `http`. The address is still printed with the last part missing: ``` 2023-06-12T15:56:58Z DEBUG your public IP address are: v4 or v6: invalid IP, v4: invalid IP, v6: aaaa:bbbb:cccc:dddd:: ```
saavagebueno commented 2025-11-20 04:21:34 -05:00
Author
Owner
Copy Link

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

No change, except that setting PUBLICIP_FETCHERS=dns now results in the same output as setting http.

Fixed in 81b336fe07 and 6513e5869a my bad that was a regression introduced with the "Environment variables parsing was changed on 12 June, please report any issue you might have"

The address is still printed with the last part missing:

What do you get with:

docker run --rm alpine:3.18 wget -qO- https://api6.ipify.org
docker run --rm alpine:3.18 wget -qO- http://ip1.dynupdate6.no-ip.com

These two urls are for IPv6 only by HTTP. Maybe it's just their response which is wrong 🤔
And also out of curiosity (this one is for ipv4 or ipv6), what do you get from:

docker run --rm alpine:3.18 wget -qO- https://domains.google.com/checkip

? Thanks!! 👍

@qdm12 commented on GitHub (Jun 12, 2023): > No change, except that setting `PUBLICIP_FETCHERS=dns` now results in the same output as setting `http`. Fixed in 81b336fe0719ff3224c70692f4ae37e086cde927 and 6513e5869adf62faa74a68b2caf99bd73fd73066 my bad that was a regression introduced with the *"Environment variables parsing was changed on 12 June, please report any issue you might have"* > The address is still printed with the last part missing: What do you get with: ```sh docker run --rm alpine:3.18 wget -qO- https://api6.ipify.org docker run --rm alpine:3.18 wget -qO- http://ip1.dynupdate6.no-ip.com ``` These two urls are for IPv6 only by HTTP. Maybe it's just their response which is wrong 🤔 And also out of curiosity (this one is for ipv4 or ipv6), what do you get from: ```sh docker run --rm alpine:3.18 wget -qO- https://domains.google.com/checkip ``` ? Thanks!! 👍
saavagebueno commented 2025-11-20 04:21:35 -05:00
Author
Owner
Copy Link

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

EDIT: fixing that bad commit 1 minute

Solved it for http: 21be712d845228f2d62790d0429474058548e1a8

TLDR: used a bad regex from a ihateregex.com which really makes me hate regex and this website.

@Ryuukyu313 can you create an issue with the logs running the latest ddns image to see why it complains about a mismatching ip address (When using dns instead, this happens:) thank you!

@qdm12 commented on GitHub (Jun 12, 2023): EDIT: fixing that bad commit 1 minute Solved it for http: 21be712d845228f2d62790d0429474058548e1a8 TLDR: used a bad regex from a ihateregex.com which really makes me hate regex and this website. @Ryuukyu313 can you create an issue with the logs running the latest ddns image to see why it complains about a mismatching ip address (`When using dns instead, this happens:`) thank you!
saavagebueno commented 2025-11-20 04:21:35 -05:00
Author
Owner
Copy Link

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

I will finish fixing it tomorrow (it's 11pm here 💤), but yeah the ipv6 regex is bad, and I can't find a decent one (and don't want to do a phd on regex either), so I'm writing my own ipv6 extraction function which will be more reliable and tested.

@qdm12 commented on GitHub (Jun 12, 2023): I will finish fixing it tomorrow (it's 11pm here 💤), but yeah the ipv6 regex is bad, and I can't find a decent one (and don't want to do a phd on regex either), so I'm writing my own ipv6 extraction function which will be more reliable and tested.
saavagebueno commented 2025-11-20 04:21:35 -05:00
Author
Owner
Copy Link

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

Fixed in 954dffd3a7

@qdm12 commented on GitHub (Jun 13, 2023): Fixed in 954dffd3a78751061c01e0f9135086a306f57dc2
saavagebueno commented 2025-11-20 04:21:35 -05:00
Author
Owner
Copy Link

@tom-a-wagner commented on GitHub (Jun 13, 2023):

@qdm12 Can confirm 954dffd3a7 fixes the issue, the correct IP address is now updated.

The mismatch error when using the dns fetcher is also no longer present, it works just fine now.
Looking at the old logs again, I'd suspect that the same faulty regex was used on the response from googledomains,
which then caused the mismatch.

And thanks a lot for your work! Out of all ddns clients I've tried, yours is now the only one I could get to work with my IPv6-only setup.

@tom-a-wagner commented on GitHub (Jun 13, 2023): @qdm12 Can confirm https://github.com/qdm12/ddns-updater/commit/954dffd3a78751061c01e0f9135086a306f57dc2 fixes the issue, the correct IP address is now updated. The mismatch error when using the dns fetcher is also no longer present, it works just fine now. Looking at the old logs again, I'd suspect that the same faulty regex was used on the response from googledomains, which then caused the mismatch. And thanks a lot for your work! Out of all ddns clients I've tried, yours is now the only one I could get to work with my IPv6-only setup.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Category: Config problem 📝
Category: Database 🗃️
Category: Documentation ✒️
Category: Foolproof settings 👼
Category: Good idea 🎯
Category: Healthcheck 🩺
Category: IP fetching 📥
Category: Label missing ❗
Category: Maintenance ⛓️
Category: Motivated! 🙌
Category: New provider 🆕
Category: Provider update ♻️
Category: Shoutrrr 📢
Category: Web UI 🖱️
Category: Wildcard 🃏
Closed: ⚰️ Inactive
Closed: 👥 Duplicate
Closed: 🗑️ Bad issue
Complexity: ☣️ Hard to do
Complexity: 🟩 Easy to do
Priority: 💤 Low priority
Priority: 🚨 Urgent
pull-request
Mirrored from GitHub Pull Request
 Status: 🔒 After next release
Status: 🔴 Blocked
Status: 🗯️ Waiting for feedback
No Label Category: IP fetching 📥 Priority: 🚨 Urgent Status: 🗯️ Waiting for feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ddns-updater#209
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?