4 ms·

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.
      - zrail 9y ago
        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.
        AFNobody 9y ago
        I'm specifically stating the idea it is cheaper was a misconception. I didn't say everyone should quit Route53.
  - Johnny555 9y ago
    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.
    - AFNobody 9y ago
      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.
xienze 9y ago
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.
- AFNobody 9y ago
  Its a question of traffic, dns health checks, etc. as much as # of domains. If you are using it to "just" host a dumb domain record, you can get that for free at your registrar or with Cloudflare.

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.
    - zrail 9y ago
      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.
      - AFNobody 9y ago
        I'm specifically stating the idea it is cheaper was a misconception. I didn't say everyone should quit Route53.
- Johnny555 9y ago
  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.
  - AFNobody 9y ago
    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.

xienze 9y ago

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.

AFNobody 9y ago
Its a question of traffic, dns health checks, etc. as much as # of domains. If you are using it to "just" host a dumb domain record, you can get that for free at your registrar or with Cloudflare.