Dyn Decided To Stop Offering Free Accounts for Dynamic DNS
dyn.com
dyn.com
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.
[1] Text-content of email in my archive dated May 10th 2013. http://pastebin.com/r6JQxU8i
That way any provider could offer it as a service without custom support in each router.
I think RFC 2136 may support this, but it's fairly complex and needs a separately defined method of authentication, so it's no wonder home routers don't let you set this up.
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.
- You have to run your own DNS service.
- And setup a PHP page on the server, which when called will update the zone file.
But the next problem is elsewhere. All routers seem to have hardcoded DDNS server names. Therefore even if you install your own service, there is no way you can call it from a router.
It would have been better if routers had accepted a "DDNS protocol" + "a server IP" instead.
I have my home linux server. But I can't share this solution with my friends that don't run home servers.
Both OpenWRT and DDWRT are reputable firmwares which supports a wide array of routers.
Personally, I always pick routers I can run a custom firmware on (have run {DD-,Open}WRT). DD-WRT has an additional field for a single url to update IP. I use namecheap's API endpoint there.
[1] https://www.namecheap.com/support/knowledgebase/category.asp...
I've been thinking about this prior to this announcement.
The way I am planning to (try to) solve this is by way of a cron script running on the host box at the location with the non static ip address.
The cron script running ever minute "gets" a page on a remote server [1] (say using curl). Actually see [2].
Another script running on the remote server monitors the apache logs and notes when the particular page is requested (along with some possibly unique and changing random number). Another script then takes that IP and updates the dns server that you have running and restarts it.
All of this should be able to be done with shell scripting and use of cron.
Thoughts? I'm not proposing this as a robust solution to everyone's issues but I think it will work.
[1] ssh to the server and gets the page locally or by VPN so that the page being requested is obscure.
[2] Of course I guess you could cut just out the apache part and also just ssh into the server, do "last" piped into "cut" then nslookup and get it that way as well.
It checks if current IP has been changed since last run, and if yes, sends an API request to my VPS provider to update a DNS A record with the new value.
Here is a sample script with Linode and DigitalOcean API calls: https://gist.github.com/Hangya/10026019
You could be left with a long window before your hosts IP gets updated by your local DNS cache.
Oh, well. Time to move on.
If anyone here is using DD-WRT, take a look at these instructions before trying to set up your freedns subdomain (needs a token instead of login/password): extracted from http://www.dd-wrt.com/wiki/index.php/DDNS_-_How_to_setup_Cus...
Go to http://freedns.afraid.org/dynamic/ and login with your normal username and password for the freedns service. Click "Direct URL" on the domain you would like to be set to your WAN IP address. Copy everything from the right of the ? in the address bar.
Router Settings: DDNS Service: freedns.afraid.org User Name: USERNAME Password: PASSWORD Host Name: yourdomain.com,What_You_Copied_Before Force Update Interval 10
(Note: Since afraid.org doesn't require a username and password when doing a "wget-style" update, you can also just do the following to keep from exposing your username and password: User Name: guest Password: guest)
I've been happily using it for years, and Josh is very responsive if you have problems or questions.
Mostly because 1. it's free and 2. it was one of the listed providers supported by my OpenWRT router[1].
While I'm not against paying for services per se, I didn't really feel like one simple host was worth shelling out $20 for on an annual, perpetual basis.
I think that the offering when I signed up was two free zones. Now it looks like you can get one for free, unless I'm just grandfathered in.