I used to work for Bytemark, being a sysadmin and sometimes handling support requests from end-users, along with their clients.
One thing that never got old was marking DNS-related tickets as "resolved", or managing to slip that word into replies.
Similarly being married to a Finnish woman you'd be amazed how often Finnish and Finished become interchangable.
Anyway that's enough pun-discussion.
Over the past few days I've, obviously, been playing with DNS. There are two public results:
This is my simple Dynamic-DNS host, which has now picked up a few users.
I posted a token on previous entry, and I've had fun seeing how people keep changing the IP address of the host skx.dhcp.io.. I should revoke the token and actually claim the name - but to be honest it is more fun seeing it update.
What is most interesting is that I can see it being used for real - I see from the access logs some people have actually scheduled curl to run on an hourly basis. Neat.
This is a simple lookup utility, allowing queries to be made, such as:
Of the two sites this is perhaps the most useful, but again I expect it isn't unique.
That about wraps things up for the moment. It may well be the case that in the future there is some Git + DNS + Amazon integration for DNS-hosting, but I'm going to leave it alone for the moment.
Despite writing about DNS several times in the past the only reason this flurry of activity arose is that I'm hacking some Amazon & CPanel integration at the moment - and I wanted to experiment with Amazon's API some more.
So, we'll mark this activity as resolved, and I shall go make some coffee now this entry is Finnish.
ObRandomUpdate: At least there was a productive side-effect here - I created/uploaded to CPAN CGI::Application::Plugin::Throttle.
The simplest possible DNS-based service which I could write to explore Amazon's DNS offering has to be dynamic DNS, so I set one up..
The record skx.dhcp.io can be updated to point to your current IP by running:curl http://dhcp.io/set/efa6961c-f3dd-11e3-955b-00163e0816a2
Or to a fixed IP:curl http://dhcp.io/set/efa6961c-f3dd-11e3-955b-00163e0816a2/18.104.22.168
The code is modular and pretty nice, and the Amazon integration is simple.
(Although I need to write code to allow users to sign-up. I'll do that if it seems useful, I suspect there are already enough free ddns providers out there - though I might be the first to support IPv6 when I commit my next chunk of work!)