I used to do this as well, with tinydns. I even wrote an article with a similar name[1]. Then I wrote another article with a similar name[2] when I decided that I was being silly.
I use Route53 now with a little cron that periodically updates the record that points at my home IP[3]. Route53 is bulletproof in a way that I'm unable to accomplish on my own.
edit: Route53 is not actually cheaper than this person's setup. That said, $0.50 per hosted zone is a bargain for what you get and there's a volume break to $0.10 after 25 zones. We're talking about global 100% DNS uptime with an SLA[4] for $0.50/mo.
I do it for free by using cloudfare as the dns provider and used to do it for free by using the Linode DNS service that comes included with having a VM there.
+1 for linode. That's what I use for DNS. Previously I used dns.he.net which is free. I highly recommend it if you don't want to pay anyone for anything.
I do the same thing (pointing a Route53 entry to my IP) with a script that runs on a Raspberry Pi in my living room. Very happy with the setup, though Cox changes my address so infrequently that it's almost unnecessary. In the name of sharing a python implementation, or maybe just shameless self-promotion, here's mine: https://github.com/benrad/pydydns
This is exactly what I do with PfSense. I run multiple services from home, so get PfSense to keep a Route 53 address of home.<domain>.com updated to point to my home IP, then create CNAMEs for each service that point to that home record.
It's then just a case of using HAProxy (which is also on the same box) to route to different internal services. I don't host anything important, just time saving things running in docker containers on a separate box. Things like email and personal site always go on cloud hosting or a service, since these need to be up for me.
Make sure your firewall rules are setup well, and look into some logging and monitoring.
Same here, but I do it for free by using the DNS of my registrar which has an API (this is gandi.net and their new API is extremely simpke and useful).
That may be true, but few home users have 1000 domains to manage, and for the ones that do, they can do the math and decide what is most cost effective.
My company hosts several hundred domains, and using Route53 was a no-brainer -- even if the hardware is free, monitoring, patching and maintaining those bind servers is much more expensive than route53 even if we had 1000 domains.
it is cheap. because human time is always worth more than paying for routes, requests and healthchecks (ps. you won't get healthchecks that easily with your own setup, especially not health checks that will remove/add servers from your dns.)
> it is cheap. because human time is always worth more than paying for routes, requests and healthchecks (ps. you won't get healthchecks that easily with your own setup, especially not health checks that will remove/add servers from your dns.)
Do you genuinely not understand I'm talking about a production setup that already exists?
Like, if you think health checks are non-trivial you probably shouldn't be running your own DNS.
You clearly have needs that don’t match with the majority. That’s fine! I see nothing wrong with that. Arguing that Route53’s value proposition doesn’t fit your needs and therefore doesn’t fit anyone’s is disingenuous.
Are you genuinely unaware of how little they charge for requests?
Our last bill showed around 100 million queries last month, so that cost around $40.
We've got a dozen healthchecks, so that's another $6. $0.50 each is essentially free compared to the time it'd cost us to set up the equivalent healthcheck service with bind.
150 domains costs another $25
So our entire bill for 150 domains and a around 3M DNS queries/day is around $75/month.
So you use AWS for their hosting and want to stay in their "world", fine. I don't use AWS for hosting either and my equivalent of 12 health checks ends up being $33 which gets over the $100 figure I mentioned earlier.
If it genuinely takes you an hour a month to maintain your own setup, I guess your logic makes sense but for me it doesn't.
You've also basically admitted its alot less than 1k domains.
If I hosted with AWS, it would massively inflate my hosting costs as well. Lol.
Do you actually have that many domain names or are you counting subdomains? Because Route53’s 50 cent charge is per zone, so you can go nuts with subdomains for no extra charge.
I use Route53 now with a little cron that periodically updates the record that points at my home IP[3]. Route53 is bulletproof in a way that I'm unable to accomplish on my own.
edit: Route53 is not actually cheaper than this person's setup. That said, $0.50 per hosted zone is a bargain for what you get and there's a volume break to $0.10 after 25 zones. We're talking about global 100% DNS uptime with an SLA[4] for $0.50/mo.
[1]: https://www.petekeen.net/how-i-run-my-own-dns
[2]: https://www.petekeen.net/how-and-why-im-not-running-my-own-d...
[3]: https://github.com/peterkeen/route53_ddns
[4]: https://aws.amazon.com/route53/sla/