What's disturbing is the number of products which have dyn.com integration built in. Nearly every ADSL modem I've had in the last 10 years has had a username/password field for their service.<p>It would have been great if they could have monetized that existing base - instead, hundreds of thousands of users will wake up one day next month and things will have mysteriously stopped working.
I was a free-rider of their free tier for a while, but I totally understand and respect their decision. My main problem is not that I do not want to pay 20-30$ a year for a dynamic DNS, my problem is that it is either one of their domains or I have to bring domain services to them.<p>I own a VPS, I own a domain and I was wondering if I could do something myself. Does anyone have any recommendations how to set up DIY dynamic DNS? I would like home.mydomainexample.com or even home.homelan.mydomainexample.com to point to my home dynamic IP.
Early donors still get their free account as promised. Faith in humanity restored. I am proud to be part of the early DynDNS history in this small way.
<a href="http://zonomi.com" rel="nofollow">http://zonomi.com</a> may be useful for the "i have a domain but don't want to DIY a DynDNS replacement" crowd. A single zone with up to 10 records can be hosted for free, and one of the features is a simeple GET based update API for DynDNS style operation.
What's the easiest way to run your own dynamic DNS service with your own domain? I'm guessing something like Amazon's Route 53 with an updater script, such as <a href="https://gist.github.com/natlownes/2061658" rel="nofollow">https://gist.github.com/natlownes/2061658</a>
Rackspace offers DNS with all cloud accounts and doesn't charge for it and as far as I know, you can sign up for a cloud account and not actually purchase any services, though I would probably put some files in Cloud Files so you're at least paying them something to keep the account around. You can update your records via their API or via their control panel and there are no per-change or per-domain fees.
Oh, I remember using dyndns back in the day. It was remarkably convenient to run Apache on my desktop computer, I could just drop files to my www directory and have link ready to be pasted on IRC. Of course that was way before Dropbox et al came to be.
I used to pay for a subscription, but I canceled it because I was using it for two hosts only. They are now offering a subscription for 20 dollars, which I think is very expensive considering the two hosts I need.<p>Oh, well. Time to move on.
Two of the default options on my router are DynDNS and NoIP. They both have paid plans. Is there anyone with experience with both providers who can compare the pros and cons of these services?