What Is Dynamic DNS and How Does It Keep a Branch Reachable?
A remote branch gateway may receive a different public IP address when its internet connection reconnects. A monitoring team using the old address then loses its way to the site. A dynamic DNS service keeps a stable hostname associated with the changing address, so operators can find the gateway without manually distributing each new IP.
What Is a DDNS Update Client?
Dynamic DNS, or DDNS, is a method for automatically updating a DNS record when an address changes. A router or a separate update client observes the address and sends an authenticated update to the DNS provider. The provider changes the record served by its authoritative name servers. No-IP describes this sequence, including the use of a router or its update client and a provider-issued credential.
Consider a gateway with the hostname branch.example.com. In an illustrative IPv4 example, its public address changes from 192.0.2.10 to 192.0.2.25 after a reconnect. These addresses are reserved for documentation; they are not actual branch endpoints. The update client detects the new public address and submits it to the provider. An authorized update changes the hostname’s A record to 192.0.2.25. A comparable AAAA record holds an IPv6 address when that is the address being maintained.
What is a dynamic DNS record in this setting? It is an ordinary address record kept current by an update process. Clients still look up the same hostname. The change is in the address returned, not in the name operators enter. What is a DDNS update client responsible for? It must run reliably, detect the appropriate address, and authenticate to a provider permitted to change the record.
The meaning of dynamic DNS becomes clearer when ownership is assigned: someone must maintain the updater, protect its credential, and monitor failures. A token restricted to the necessary zone and DNS permissions reduces the scope of an exposed credential. For example, Cloudflare’s record-update API requires DNS write permission and supports API tokens. The exact update mechanism and permissions vary by provider.
Record freshness and connection paths
An authoritative update is not always immediately visible to every user. Recursive DNS resolvers and local clients may cache the earlier answer for its time to live (TTL). A shorter TTL can reduce how long a cached answer remains valid, but causes more frequent lookups. Cloudflare’s DNS documentation notes that the previous record can remain cached until its TTL expires. A lower TTL set only after an address changes does not erase answers already cached under the old TTL.
The purpose of dynamic DNS is to keep the name-to-address mapping current; reaching the application requires a separate working network path. A gateway behind carrier-grade NAT may share a provider-controlled public IPv4 address, so updating a record to that address does not make unsolicited inbound traffic reach the branch. Firewall rules and any required forwarding must also permit the intended connection. No-IP’s guidance explicitly distinguishes DDNS from bypassing carrier-grade NAT or opening a network.
For a branch without a usable inbound path, an outbound tunnel or a VPN designed for the network may provide a different route. The choice depends on where each endpoint initiates its connection and the organization’s access policy. DDNS can support a hostname used in that design, but it does not replace authentication, routing, or firewall policy.
Validate the record and the service
A successful update response confirms that the provider accepted a change; the record and the service should still be tested separately. Query the authoritative name server for the hostname and the relevant A or AAAA record. Compare its answer with the gateway’s current public address. Then query a recursive resolver to see what an ordinary client receives and inspect the updater’s logs if the authoritative answer remains old.
For the final reconnect test, reconnect the branch link and confirm that the authoritative record changes to the new public address. Allow for the previous cache TTL, then test the intended service from outside the site network. A correct DNS answer with a failed service test points the investigation toward the route, firewall, forwarding, or application rather than the record alone.