1. 10
  1.  

  2. 2

    Maybe I missed it, but looking through the docs at the capabilities I cannot see the advantage of using this over just using a language of your choice and it’s version of Template::Toolkit.

    Once you outgrow handcrafting your config, though DnsControl still has you handcrafting but code instead, I suspect failover is now of growing importance to you as well as WRR load-balancing. DnsControl seems not to cater for this, maybe I missed it in their documentation?

    Interestingly I always found when small using a DNS hoster makes a lot of sense. Once you need failover it actually is better to bring DNS in-house. The one exception is if you are globally latency sensitive then maybe outsourcing lets you avoid the ballache of needing to wear a BGP wizards hat to run an anycast service.

    Running your own global DNS service is straight forward and actually not that scary, I personally think hosting an HTTP or SMTP service is harder.

    My recommendation for those feeling they are outgrowing their hosting DNS provider, look to gdnsd and run it on a number number of VPS servers sourced from varying providers.

    The failover can be backed by one of the few built in probes, but the best part is it can call an external script and use the exit code for signaling. Now you can plug in your local Nagios or query Graphite!

    For me, it was the only solution (hosted DNS failed me) that supported a geo targetted WRR response where the multiple records returned would not contain the IPs of two servers provided by the same vendor; my last job we had 50 leased servers from 20+ different providers.

    1. 1

      Soooo, h2n but for the cloud?

      1. 1

        Looks a lot like the lua-based, and excellent http://www.luadns.com/.

        1. 1

          No, completely different.

          The syntax looks nearly identical, has the same ‘poor choice’ of just macro’ifying what you would just put in a BIND zone file anyway, but there the similarity ends.

          DnsControl lets you use a hosted provider of your choosing. LuaDNS forces you to use their hosted service only.

          1. 1

            The syntax looks nearly identical

            I suppose that is why I thought it looks a lot like luadns.