Keep your dynamic DNS updated with your current public IP address

Checks your public IP on a schedule and updates Namecheap's DNS so your domain always points to the right place.

How the work actually flows

It branches. Exactly one path is taken; runs once per each subdomain.

Pattern: Exclusive Choice (4) · Multiple Instances without Synchronization (12)

flowchart TD trig(["regular scheduled check"]):::trigtime s0["Check current public IP"]:::task s1[["Compare against subdomain records"]]:::mi trig --> s0 s0 -->|"one per each subdomain"| s1 gx{"× IP address changed"}:::gate s1 --> gx p00["Update Namecheap DNS record"]:::task gx -->|"IP changed"| p00 p10["Leave record as is"]:::task gx -->|"IP unchanged"| p10 p00 --> out p10 --> out out[/"DNS record matching current IP"/]:::out pay{{"Hosted services stay reachable"}}:::pay out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepRuns once per itemOne path onlyResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
General Automation
Connects
Namecheap

The problem it solves

If your internet provider changes your home or office IP address, anything you host there, like a personal server or remote access tool, becomes unreachable until you manually update your DNS settings. Checking and updating this by hand is easy to forget.

Who it fits

Anyone self-hosting a server or service from a location without a fixed IP address.

How it works

  1. On a regular schedule, the system checks your current public IP address
  2. It compares that to what's on file for each of your subdomains
  3. If the IP has changed, it updates Namecheap's dynamic DNS with the new address
What you get

Servers you can always reach from anywhere

Your self-hosted server stays reachable at the same address even when your internet provider changes your public IP address.

What you get

An always-current DNS record, so your domain keeps pointing to your server even after your IP changes.

What you need

A Namecheap domain with dynamic DNS enabled.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook