The Dynamic DNS URL:
https://dynamic.zoneedit.com/auth/dynamic.html?host=<your_hostname>&dnsto=<your_ip>
has been retained and will continue to function for backwards compatibility with all existing ZoneEdit dynamic DNS clients.
The non-SSL URL will also work:
http://dynamic.zoneedit.com/auth/dynamic.html?host=<your_hostname>&dnsto=<your_ip>
although you should probably stop using it (also see "auth tokens" below).
We've added a DYN endpoint for creating TXT records which can be used to
validate Lets Encrypt certificates. The credentials to use are the same as for DYN updates. An example of the parameters that need to be passed:
https://dynamic.zoneedit.com/txt-create.php?host=_acme-challenge.example.com&rdata=depE1VF_xshMm1IVY1Y56Kk9Zb_7jA2VFkP65WuNgu8W
And to tidy up these TXT records afterwards, there's a delete endpoint:
https://dynamic.zoneedit.com/txt-delete.php?host=_acme-challenge.example.com&rdata=depE1VF_xshMm1IVY1Y56Kk9Zb_7jA2VFkP65WuNgu8W
Things To Know About Dynamic DNS On The New System
- Dynamic hostnames use the "DYN" pseudo-record type
To create a new host record that you plan to use with Dynamic DNS you actually create a record of type "DYN", not a regular host record.
- If you update a Hostname/A Record dynamically it will become a type 'DYN' record
This was done to preserve backwards compatibility with existing domains and clients. You can still manually edit or modify a DYN record like any other kind of A record.
- You can, and should use 'auth tokens' in your Dynamic DNS updates rather than your account level password
Legacy ddns clients used your ZoneEdit username and password combo to authenticate Dynamic DNS requests. This is still allowed for backwards compatibility and will be permitted for some unspecified amount of time (at some point we will force switch over to auth tokens).
