Feature request: Allow custom IP resolver on a per domain basis #252

New Issue

saavagebueno · 2025-11-20T04:22:01-05:00

saavagebueno commented

2025-11-20 04:22:01 -05:00

Originally created by @Nystik-gh on GitHub (Feb 3, 2023).

Originally assigned to: @qdm12 on GitHub.

I think adding support for per domain IP resolution could be a useful feature.

I have two servers with different external IPs, one is my main server (SERVER_1), one is a low powered device where I want to run as few services as possible (SERVER_2). I currently run DDNS on SERVER_1. Now I need to provide DNS updates for SERVER_2 as well, but I would prefer to only have to maintain one instance/configuration of DDNS, rather than have an instance running on both servers.

My current intention is to forward the service on SERVER_2 over SSH to SERVER_1, and effectively use SERVER_1 as a proxy.
However, in the event that SERVER_1 goes down, I will no longer be able to access SERVER_2. It would be beneficial if DDNS could also update a separate domain with the IP of SERVER_2.

Example of how the config could look for my usecase:

[
    { 
        "provider":  "dreamhost",
        "key": "...."
        "domain": "SERVER_2.proxy.mydomain.com",
        "ip_version": "ipv4"
    },
    {
        "provider":  "dreamhost",
        "key": "...."
        "domain": "SERVER_2.mydomain.com",
        "ip_resolver": "http://localhost:3333/ip",
        "ip_version": "ipv4"
    }
]

In this case, http://localhost:3333/ip is a tunneled service from SERVER_2 which will provide the external IP of SERVER_2.

Originally created by @Nystik-gh on GitHub (Feb 3, 2023). Originally assigned to: @qdm12 on GitHub. I think adding support for per domain IP resolution could be a useful feature. I have two servers with different external IPs, one is my main server (SERVER_1), one is a low powered device where I want to run as few services as possible (SERVER_2). I currently run DDNS on SERVER_1. Now I need to provide DNS updates for SERVER_2 as well, but I would prefer to only have to maintain one instance/configuration of DDNS, rather than have an instance running on both servers. My current intention is to forward the service on SERVER_2 over SSH to SERVER_1, and effectively use SERVER_1 as a proxy. However, in the event that SERVER_1 goes down, I will no longer be able to access SERVER_2. It would be beneficial if DDNS could also update a separate domain with the IP of SERVER_2. Example of how the config could look for my usecase: ```json [ { "provider": "dreamhost", "key": "...." "domain": "SERVER_2.proxy.mydomain.com", "ip_version": "ipv4" }, { "provider": "dreamhost", "key": "...." "domain": "SERVER_2.mydomain.com", "ip_resolver": "http://localhost:3333/ip", "ip_version": "ipv4" } ] ``` In this case, `http://localhost:3333/ip` is a tunneled service from SERVER_2 which will provide the external IP of SERVER_2.

saavagebueno added the Priority: 💤 Low priority Category: Good idea 🎯Complexity: ☣️ Hard to do labels 2025-11-20 04:22:01 -05:00

saavagebueno referenced this issue

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

[PR #252] [MERGED] add support aliyun dns #667

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#252