http://nexus.zteo.com/blog/your-own-dynamic-dns-in-3-steps/
Interesting idea, perhaps provides a little bit of added flexibility (and reduced cost) compared to Dyn, though I don’t have any complaints about Dyn at this point. Also review the DDNS and TSIG articles on Wikipedia as well as RFC2136. Still thinking that perhaps a hybrid HTTPS method; would allow any web server one had available to potentially be able to serve as a receiver for the updates as long as it had at least enough outbound access to give the information to the BIND server, allowing for possibly a bit more obscurity in the update path; also wouldn’t require that whatever host received the update information not have BIND running (i.e., perhaps a web host) as long as it could establish an outbound communication to the BIND server – or write to some file that the BIND server could retrieve.
Interesting question therefrom – short of a VPS, is it possible to use client-side certificates to identify a client to a webserver? How about self-signed client certificates?