1. 30
  1.  

  2. 6

    One of the best reasons to run DNS on your own for a while, is to learn. DNS is a core technology of how stuff becomes accessible on the Internet and one of a few that you can run at home “in production” that will allow you to learn how stuff works and how to debug looking at other places too.

    The maxim “everything is a DNS problem” is not wrong. It might indeed be a DNS issue, or a reachability issue, or even something else that first manifests itself in DNS.

    So running it for a while in order to get a feeling of how stuff works is a good thing.

    1. 5

      Soother reason can be that the current DNS server doesn’t allow certain record types. This becomes more rare but it has been the case, especially for more rarely used record types stuff as SSHFP..

      Some (also more rare nowadays) don’t provide an option for DNSSEC.

      I don’t know the exact circumstances anymore, but at a company I once worked we got locked out of CloudFlare and despite being a paying customers or took a pretty long time to reach their support. So I’d recommend at least having an up to date list of all records stored somewhere, in case of such emergencies.

      1. 2

        do something weird and custom

        My favorite example of this is the Solar Protocol. :D

        1. 2

          Servers, please, not server.

          Most service businesses that deal with DNS (registrars, hosters, ISPs…) will happily run a secondary zone for free or very low cost. Not only is this educational, it vastly improves your availability.

          At a business or home setting, you likely have at least two always-on machines anyway, so making them both resolvers is a good idea, If you want to learn mulitple software packages, having one run BIND and the other unbound or something else is a nice lesson in interoperability.

          1. 1

            One of the reasons I run a DNS server is the ability to set low TTLs. I’m not in the market for TTLs >= 1h which I get from my registrar.