Catch a DuckDNS subdomain that stopped updating
Every hour, WebRun opens your DuckDNS account, checks the last successful IP update time for each of your subdomains, posts a Telegram alert naming any subdomain that has not updated within the expected window, and sends you a direct Twilio text if one has been stale for more than 24 hours.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I know if a DuckDNS subdomain stopped updating?
Every hour, WebRun checks the last successful IP update time for every subdomain in your DuckDNS account. It posts a Telegram alert naming any subdomain that has gone stale and sends you a direct Twilio text if one has not updated in over 24 hours, so a silent outage does not go unnoticed.
- A stale subdomain gets flagged within the hour instead of discovered by accident
- An update gap over 24 hours triggers a direct text, not just a channel post
- Every subdomain on the account gets checked, not just the ones you remember
Built for home lab operators · self hosted service owners · hobbyist developers · DuckDNS users
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.duckdns.orgin a real browser with your saved login - no setup, no API keys. -
1
DuckDNS - check each subdomain's last update time
- Open your DuckDNS account and list every subdomain you manage
- Check the timestamp of the last successful IP update for each
- Flag any subdomain that has not updated within its expected refresh window
Done when Every subdomain's last update time is captured and checked.
-
2
Telegram - alert Telegram for a stale subdomain
telegram.org How to Automate Telegram
WebRun opens Telegram to alert Telegram for a stale subdomain. - Post a Telegram alert naming any subdomain that has gone stale
- Include how long it has been since the last successful update
- Stay quiet when every subdomain has updated within its expected window
Done when Telegram has an alert for every stale subdomain this run.
-
3
Twilio - text you if it has been stale over 24 hours
twilio.com How to Automate Twilio
WebRun opens Twilio to text you if it has been stale over 24 hours. - Send yourself a direct Twilio text if a subdomain has been stale for more than 24 hours
- Name the subdomain and the last known update time
- Send only to your own saved number
Done when A text has gone out for any subdomain stale more than 24 hours.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it fix the update or restart anything on the client device?
No. WebRun only reads the last update timestamp DuckDNS reports and alerts on it. Fixing the client sending the update always stays a step you take.
Why would a subdomain stop updating?
Common causes include the client script or device losing network access or a router being replaced, but WebRun reports the gap rather than diagnosing the client side cause.
Why the extra text after 24 hours?
A subdomain used for remote access or a home server can become unreachable once it goes stale, so a longer gap gets a direct text as well as the Telegram alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.