With DynDNS shutting down their free dynamic DNS service quite a few customers contacted us to ask for an upgrade to our DNS API so that it can effortlessly substitute in for DynDNS. For example we saw this request over twitter.
Several people offered a suggested implementation. They all asked for something along these lines,
Can you make it so that when you put an update for an A record through
it can substitute in the calling IP address instead of supplying one.
It’s clear that many of our customers still don’t instinctively get the implications of dual stack hosting yet.
In particular if you call the API from a v6 address and ask for an update to your A record it will fail because it doesn’t know your v4 address. Similarly if you call it from a v4 address and ask for an update to your AAAA record, it will also fail for precisely the same reason. You have to call the API to update your A or AAAA record over the correct v4/v6 channel in order to get the correct update, and if you’re dual stack you need to call it twice.
We decided that we should fasttrack this project, and gave it to Liam Fraser – who’s back with us during his Easter holidays. We’re proud to present our fully documented and enhanced Dynamic DNS API which sample code for single (v4 or v6) and dual (v4 and v6) stack hosts.
We include our DNS API free of charge for anyone who’s bought a domain name from us, so if you’d like to use our Dynamic DNS service, create an account at our control panel and follow the instructions.
If you’re bored of working for a company where you can’t get things done, and would like to work somewhere where you can implement, test, document and release a small enhancement in about six hours, you can apply for a job with us here. We’re especially interested in talented graduates and school leavers who know their Linux.