Show HN: A simple-to-update dynamic DNS service
1–10 of 28 posts
Re: Show HN: A simple-to-update dynamic DNS service
#2Re: Show HN: A simple-to-update dynamic DNS service
#3Simple and to the point. Truth be told I've always wanted something like this for my own domains, so that I can point to a home machine, but was too lazy to set it up. Thanks for throwing this out here!
Initially it was put together as a learning experience, but I can see that it is useful enough to remain live indefinitely.
I can imagine several way of monetizing it, such as adding the MX/SRV/TXT/CNAME records, etc. But the one that seems most useful would be allowing custom domain - and sadly I can't see how to do that easily.
(I can't imagine somebody would trust me with their root-domain, basically. And having *.foo.example.com seems like it would be long enough to spoil the utility.)
Re: Show HN: A simple-to-update dynamic DNS service
#4Simple and to the point. Truth be told I've always wanted something like this for my own domains, so that I can point to a home machine, but was too lazy to set it up. Thanks for throwing this out here!
You're welcome. Initially it was put together as a learning experience, but I can see that it is useful enough to remain live indefinitely. I can imagine several way of monetizing it, such as adding the MX/SRV/TXT/CNAME records, etc. But the one that seems most useful would be allowing custom domain - and sadly I can't see how to do that easily. (I can't imagine somebody would trust me with their root-domain, basical…
The “root-domain” is the domain name with a single zero-length label at the top of the hierarchy. What you're referring to is a zone.
Re: Show HN: A simple-to-update dynamic DNS service
#5Earlier quoted context omitted.
You're welcome. Initially it was put together as a learning experience, but I can see that it is useful enough to remain live indefinitely. I can imagine several way of monetizing it, such as adding the MX/SRV/TXT/CNAME records, etc. But the one that seems most useful would be allowing custom domain - and sadly I can't see how to do that easily. (I can't imagine somebody would trust me with their root-domain, basical…
I can't imagine somebody would trust me with their root-domain, basically. The “root-domain” is the domain name with a single zero-length label at the top of the hierarchy. What you're referring to is a zone.
Re: Show HN: A simple-to-update dynamic DNS service
#6 crontab -e
and adding the line: 31 * * * * curl http://dhcp.io/set/99351a76-f6...
(the above job will run on the 31st minute of every hour)Re: Show HN: A simple-to-update dynamic DNS service
#7Nice! Setting up my server to update every hour was as simple as: crontab -e and adding the line: 31 * * * * curl http://dhcp.io/set/99351a76-f6... (the above job will run on the 31st minute of every hour)
Re: Show HN: A simple-to-update dynamic DNS service
#8Earlier quoted context omitted.
I can't imagine somebody would trust me with their root-domain, basically. The “root-domain” is the domain name with a single zero-length label at the top of the hierarchy. What you're referring to is a zone.
I thought context would make that clear, but yes you're correct.
Re: Show HN: A simple-to-update dynamic DNS service
#9Nice! Setting up my server to update every hour was as simple as: crontab -e and adding the line: 31 * * * * curl http://dhcp.io/set/99351a76-f6... (the above job will run on the 31st minute of every hour)
I suspect that you'll want to hide STDOUT, if not STDERR. If you're ever dual-homed you might also want to consider adding an explicit "-4", or "-6" in there.