How Agent-based dynamic DNS works
Edgekeeper receives the public IPv4 reported by a Docker Agent on your own server or network. It does not use the public IP of the hosted Edgekeeper service as your server address. Each managed domain is assigned to an Agent, so different locations can update independently.
- Run an Agent at the location hosting your application.
- Connect the provider that hosts the domain’s authoritative DNS.
- Set the domain’s baseline IPv4 to the address currently used by the A records you want to manage.
- When the Agent reports a changed IP, Edgekeeper updates the matching managed A records and records the result.
Choose the DNS host, not just the registrar
Cloudflare, Namecheap and GoDaddy are supported DNS providers. A domain purchased through GoDaddy but using Cloudflare nameservers belongs in the Cloudflare integration. You do not need to transfer the domain registration.
Connect your own provider API credentials and ensure they have the required access to the selected zone or domain. Provider API eligibility and network restrictions still apply; an Edgekeeper subscription does not grant access to a provider API.
Set the baseline carefully
The baseline is configured per domain, not globally. For example, if home.example.com and vpn.example.com point to 203.0.113.42, that baseline identifies A records to manage at that location. Do not include records pointing to unrelated servers. Review discovered records before enabling automation.
Automatic IP synchronization targets A records. Manual DNS record creation, editing and deletion is a separate plan permission, and supported record fields depend on the provider. Cloudflare proxy settings and record TTL are preserved during automatic updates.
Permissions, caps and troubleshooting
DNS automation is one plan permission covering all supported DNS providers. Cloudflare, Namecheap and GoDaddy domain caps are counted separately, not as a combined total. Check Billing for your workspace’s actual access and limits.
If records stop updating, check the assigned Agent’s live status, domain pause state, provider credentials and synchronization activity. Paused resources and offline Agents are not eligible for automatic updates. Provider errors or rate limits can delay a sync; repeated manual clicks do not resolve those restrictions.
DNS updates do not create port forwarding, bypass carrier-grade NAT or make an unreachable server publicly accessible.