5 ms·

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

by zrail 9y ago

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. [1]: https://www.petekeen.net/how-i-run-my-own-dns https://www.petekeen.net/how-i-run-my-own-dns [2]: https://www.petekeen.net/how-and-why-im-not-running-my-own-dns https://www.petekeen.net/how-and-why-im-not-running-my-own-d... [3]: https://github.com/peterkeen/route53_ddns https://github.com/peterkeen/route53_ddns [4]: https://aws.amazon.com/route53/sla/ https://aws.amazon.com/route53/sla/

HorizonXP 9y ago
Furthermore, lots of FOSS router software, like pfSense, have support for Route53 for a Dynamic DNS target, built-in.
- francis-io 9y ago
  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.
__david__ 9y ago
Are you sure it's cheaper than $2/month? I also run route53 and it comes out to about $20/month for 30ish domains.
- zrail 9y ago
  You're right. Updated.
AFNobody 9y ago
It is cheaper for you and the OP. It isn't cheaper "with a whole bunch of domains". Route53 would cost me ~$100/month vs. ~$21/month for my own setup.
- Johnny555 9y ago
  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.
  - AFNobody 9y ago
    Are you genuinely unaware they charge for DNS requests, healtchecks, etc? If you are using it to "just" host a dumb domain record, you can get that for free at your registrar or with Cloudflare. This whole "Route53 is cheap" mantra makes no sense unless you are doing something so simple you get it free with 2934902342390 other services.
    - merb 9y ago
      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.)
      - AFNobody 9y ago
        > 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.
pedrocr 9y ago
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.
- graton 9y ago
  +1 for using Cloudflare. That is what I use as my DNS provider.
  - jjeaff 9y ago
    I use cloudflare as well. And they are one of the most performant. Feels too good to be true. I wonder if the offer and it performance will last...
- BenjiWiebe 9y ago
  +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.
el_benhameen 9y ago
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 https://github.com/benrad/pydydns
BrandoElFollito 9y ago
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).

by zrail 9y ago

HorizonXP 9y ago

Furthermore, lots of FOSS router software, like pfSense, have support for Route53 for a Dynamic DNS target, built-in.

francis-io 9y ago
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.

__david__ 9y ago

Are you sure it's cheaper than $2/month? I also run route53 and it comes out to about $20/month for 30ish domains.

zrail 9y ago
You're right. Updated.

AFNobody 9y ago

It is cheaper for you and the OP. It isn't cheaper "with a whole bunch of domains". Route53 would cost me ~$100/month vs. ~$21/month for my own setup.

Johnny555 9y ago
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.
- AFNobody 9y ago
  Are you genuinely unaware they charge for DNS requests, healtchecks, etc? If you are using it to "just" host a dumb domain record, you can get that for free at your registrar or with Cloudflare. This whole "Route53 is cheap" mantra makes no sense unless you are doing something so simple you get it free with 2934902342390 other services.
  - merb 9y ago
    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.)
    - AFNobody 9y ago
      > 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.

pedrocr 9y ago

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.

graton 9y ago
+1 for using Cloudflare. That is what I use as my DNS provider.
- jjeaff 9y ago
  I use cloudflare as well. And they are one of the most performant. Feels too good to be true. I wonder if the offer and it performance will last...
BenjiWiebe 9y ago
+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.

el_benhameen 9y ago

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 https://github.com/benrad/pydydns

BrandoElFollito 9y ago

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).