Choosing a Dynamic DNS Service
I recently had a look at a few dynamic DNS services. They each provide simple HTTP interfaces for updating the the “A” record for a host (that’s the one that maps a Fully Qualified Domain Name to an IP address). In each case you must provide credentials (username and password) as URL query parameters in the HTTP request. If you want to protect those credentials then you’ll want to use SSL by specifying the https URI scheme. With most of the services I looked at I found that https wasn’t really usable because the certificates presented by those services were not valid. In each such case, the provider was using a certificate whose subject (name) failed to match the FQDN of the actual host. Only one provider presented a working dynamic DNS service with a valid certificate. Without further ado:
Service Didn’t Work At All (http scheme)
Service Did Not Present Valid Certificate (https scheme)
Service Worked and Presented Valid Certificate
So the big winner here is DNS Made Easy. It was the only service that offered a functioning, secure dynamic DNS service.