easyDNS dynamic DNS client specifications. v1.3 Apr 2001

We are always happy to have more third party clients supporting our service. It benefits us to give end users as much choice as possible between packages and platforms and it hopefully benefits the software developers as their clients incorporate support for one of the fastest growing dynamic DNS providers on the internet.

But enough hype, what follows below is what you need to know to code a dyndns client for use with easyDNS. Giving credit where credit is due, the protocol used below was adapted from the format used at dyndns.org. After evaluating various approaches out there we felt theirs was the simplest and most straightforward. There are some differences, i.e. the back_mx parameter has a different meaning to our system.

If you code a completely generic client and follow the specification below, to can perform dynamic DNS updates by executing a GET method request on the following URL:

http://members.easydns.com/dyn/dyndns.php

You can send the following parameters in the QUERY_STRING of a request, for example:

http://members.easydns.com/dyn/dyndns.php?hostname=example.com&myip=10.0.0.2

If you do code a client for easyDNS, please email our support team so we can keep you informed of any changes, enhancements, bugfixes etc.

Also, please be sure to let us know about your client, which platform it runs on and where our users can download it so we can add it to our dynamic page.


Parameters:

hostname = the full hostname being updated

tld = the root domain of your hostname, for example if your hostname is "example.co.uk" you should set "tld" to "co.uk". This field can be omitted in cases of second level domains like example.com

myip = the IP address of the client to be updated. Send "0.0.0.0" to set record to an offline state (sets record to "offline.easydns.com"). If you are behind a firewall or NAT set this to 1.1.1.1 and our system will detect your remote IP for you.

mx = use this parameter as the MX handler for the domain being updated, it defaults to preference 5

backmx = either "YES" or "NO", if "YES" we set smtp.easydns.com to be a backup mail spool for domain being updated at preference 100

wildcard = either "ON" or "OFF", if "ON" sets a wildcard host record for the domain being updated equal to the IP address specified in "myip"


Result codes are as follows:

NOACCESS = the authentication failed. This not only happens if the username/password are wrong, but if they send a hostname for a domain that isn't under the user's account

NOSERVICE = Dynamic DNS is not turned on for this domain. Each domain must have it's own dyndns flag enabled individually (by the user) in their member settings.

ILLEGAL INPUT = Self-explantory. Client sent data that is outside the allowed set for a dyn dns update.

TOOSOON = not enough time has elapsed since the last update, you need to wait at least 10 minutes between updates

NOERROR = Everything worked fine.

 




Great Customer Support

We provide responsive customer support to assist you with your domain account.
You can email our support staff anytime, day or night, or call our toll-free support line
(1-888-677-4741) during regular business hours.

   Domain Name Registration    Domain Name Transfers    E-Mail Forwarding
   DNS Service & Management    Dynamic DNS Service    Secondary DNS Service

©2010 easyDNS™ Technologies Inc. -- Privacy Policy