tunnelbroker.net #423

New Issue

saavagebueno · 2025-11-20T04:23:55-05:00

saavagebueno commented

2025-11-20 04:23:55 -05:00

Originally created by @Jason-Clark-FG on GitHub (Jul 23, 2024).

What's the feature?

Thanks for the excellent tool! Could we support dynamic updates for tunnelbroker.net. Discussion here: https://github.com/qdm12/ddns-updater/discussions/524

Extra information?

He.net's info regarding it: https://forums.he.net/index.php?topic=1994.0

FAQ: https://ipv6.he.net/certification/faq.php (Just over halfway down: My IPv4 endpoint address is dynamic. Can I still create a tunnel? If yes, what do I need to do when my IP address changes?)

Originally created by @Jason-Clark-FG on GitHub (Jul 23, 2024). 1. What's the feature? Thanks for the excellent tool! Could we support dynamic updates for [tunnelbroker.net](https://tunnelbroker.net/). Discussion here: https://github.com/qdm12/ddns-updater/discussions/524 2. Extra information? He.net's info regarding it: https://forums.he.net/index.php?topic=1994.0 FAQ: https://ipv6.he.net/certification/faq.php (Just over halfway down: **My IPv4 endpoint address is dynamic. Can I still create a tunnel? If yes, what do I need to do when my IP address changes?**)

saavagebueno added the Category: New provider 🆕 label 2025-11-20 04:23:55 -05:00

saavagebueno commented

2025-11-20 04:23:56 -05:00

@agross commented on GitHub (Oct 28, 2025):

I think this will be rather hard to achieve with the current configuration model. All (? didn't check) entries in the config define a domain to decide if an update should be made. In the case of Tunnelbroker.net, this would be something that resolves to the IPv4 address of the local tunnel endpoint. I didn't find a way to determine the current tunnel endpoint IP through plain DNS to put it in a custom provider:

{
  "settings": [
    {
      "provider": "custom",
      "domain": "what should we put here?",
      "url": "https://ipv4.tunnelbroker.net/nic/update?&username=***&password=***&hostname=12345",
      "ipv4key": "ipv4",
      "ipv6key": "",
      "success_regex": "good",
      "ip_version": "ipv4",
      "ipv6_suffix": ""
    }
  ]
}

ddns-updater has no way to determine if an update is necessary.

Other DynDNS tools separate the IP detection (sometimes called providers) from making the actual updates. I, for example, have been running ddclient with ip a output (use=if in ddclient terms) as the provider. If a new IP has been "provided" this way, updates were made and persisted in a local state file. I really badly want to replace ddclient with something else that is better maintained and more modern. This is why I ended up here.

@agross commented on GitHub (Oct 28, 2025): I think this will be rather hard to achieve with the current configuration model. All (? didn't check) entries in the config define a `domain` to decide if an update should be made. In the case of Tunnelbroker.net, this would be something that resolves to the IPv4 address of the local tunnel endpoint. I didn't find a way to determine the current tunnel endpoint IP through plain DNS to put it in a `custom` provider: ```json { "settings": [ { "provider": "custom", "domain": "what should we put here?", "url": "https://ipv4.tunnelbroker.net/nic/update?&username=***&password=***&hostname=12345", "ipv4key": "ipv4", "ipv6key": "", "success_regex": "good", "ip_version": "ipv4", "ipv6_suffix": "" } ] } ``` ddns-updater has no way to determine if an update is necessary. Other DynDNS tools separate the IP detection (sometimes called providers) from making the actual updates. I, for example, have been running ddclient with `ip a` output (`use=if` in ddclient terms) as the provider. If a new IP has been "provided" this way, updates were made and persisted in a local state file. I really badly want to replace ddclient with something else that is better maintained and more modern. This is why I ended up here.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#423

tunnelbroker.net #423

`tunnelbroker.net` #423