Support for DDNS #4661

New issue

Open

opened 2026-02-28 04:10:55 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:10:55 -05:00

Owner

Originally created by @Dqrkky on GitHub (Feb 2, 2026).

I could not find any existing issues or pull requests that provide native DDNS support for hostname updates and monitoring. This feature request focuses specifically on dynamic DNS resolution and integration, which is not addressed elsewhere.

🔖 Feature description

It would be useful to add a monitor type or option that specifically validates DDNS hostnames. This would allow users to:
Verify that their dynamic hostnames are resolving to an IP.
Receive alerts if the DDNS hostname becomes invalid or stops resolving.

✔️ Solution

In my use-case, I would like:
A DNS/DDNS monitor type that checks if a hostname resolves.
Optional validation against an expected IP or IP range.
Examples:
A single IP: 0.0.0.0
A subnet: 0.0.0.0/24
This ensures alerts only trigger if the hostname resolves outside the expected network.
Notifications triggered if the hostname cannot be resolved or resolves outside the expected range.

❓ Alternatives

Users can currently use Script monitors with nslookup or dig to manually check a DDNS hostname and compare against an IP.

📝 Additional Context

Useful for dynamic IP environments (home labs, personal servers).
Ensures uptime monitoring continues to work even when IPs change within an expected range.
Could be implemented as a native “DNS check” monitor or an option inside Ping/Script monitors.

Originally created by @Dqrkky on GitHub (Feb 2, 2026). ### 📑 I have found these related issues/pull requests I could not find any existing issues or pull requests that provide native DDNS support for hostname updates and monitoring. This feature request focuses specifically on dynamic DNS resolution and integration, which is not addressed elsewhere. ### 🔖 Feature description It would be useful to add a monitor type or option that specifically validates DDNS hostnames. This would allow users to: Verify that their dynamic hostnames are resolving to an IP. Receive alerts if the DDNS hostname becomes invalid or stops resolving. ### ✔️ Solution In my use-case, I would like: A DNS/DDNS monitor type that checks if a hostname resolves. Optional validation against an expected IP or IP range. Examples: A single IP: 0.0.0.0 A subnet: 0.0.0.0/24 This ensures alerts only trigger if the hostname resolves outside the expected network. Notifications triggered if the hostname cannot be resolved or resolves outside the expected range. ### ❓ Alternatives Users can currently use Script monitors with nslookup or dig to manually check a DDNS hostname and compare against an IP. ### 📝 Additional Context Useful for dynamic IP environments (home labs, personal servers). Ensures uptime monitoring continues to work even when IPs change within an expected range. Could be implemented as a native “DNS check” monitor or an option inside Ping/Script monitors.

deekerman added the

A:monitor

help

labels

2026-02-28 04:10:55 -05:00

deekerman commented

2026-02-28 04:10:57 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 2, 2026):

I think this can be done reasonably simple using the existing DNS monitor and it's conditions.
Where do you area a concrete need?

@CommanderStorm commented on GitHub (Feb 2, 2026): I think this can be done reasonably simple using the existing DNS monitor and it's conditions. Where do you area a concrete need?