DNS update protocol
Microtech's DNS update protocol is described below. This simple to use protocol can easily be integrated into scripts, routers etc.
The HTTP requests can be made in HTTPS (secure) or plain HTTP modes. HTTP requests will be accepted on ports 80 and 8147. Port 8147 is usefull for bypassing ISP's stealthy proxies. HTTPS requests are accepted on port 443.
Single line authentication and update
|username||This can be either the account username (email address) or the name of an individual dynamic domain on your account. If the account name is specified all domains on the account are updated. Update single domains separately by specifying the domain name.|
|pass||The account password|
|hb||1 or 0. Indicates whether our system should send out heartbeats and set the domain offline if they are not responded to.|
|stealth||1 or 0. Indicates whether the offline page redirection should be made in a hidden frame to attempt to retain the original URL in the browser.|
|port||HTTP Port number. If port is 80 DO NOT USE. This option is used if your ISP blocks port 80 and you want to run a web site on an alternative port number. Please note, as this is designed to redirect HTTP requests it will only function on the 'www' record of your domain.|
|ip||Optional. If included sets your domain to point to the specified IP address. If not specified the system will auto detect your IP and set it accordingly.|
|offlineurl||The URL you would like http visitors re-directed to if you are marked off-line. Must a FULL url in the format 'https://www.youdomains.com/url'.|
|offlinetext||The message to display to http visitors when you are off-line|
|mx||Specifies an MX record. Specify server name in full with a terminating period.|
Clients should ensure that it is not possible to set automatic forced updates more than once every 10 minutes. Doing so will get your account blocked. Clients should pass the client name in http requests making it possible to log statistics as to which clients are being used and to hjelp track any possible problems.
Clients should check to see if an update request is required before sending it. Updates that are not required are logged and considered abusive as it wastes system resources. Excessive abusive updates will result in the users account and/or requests from the client being blocked.
Should you have any queries regarding the update protocol, please let us know