i've looked around for a few of those... what are the criteria?
what's the rationale for now hosting our own DNS anyways?
in $previous_job, we setup VM exchanges with other organizations to spread the service around, it worked well and also made for extra PoPs for running monitoring, bouncers and other stuff...
not sure which step to take next here, Greenhost doesn't have GeoDNS for their DNS service and don't think anycast is worth it. also, they don't have a good API for external DNS service, so it's not a good option for us right now.
giving this back to the pool so someone else can look into this.
From the Brussels notes, linked in description:
Right now, we do our own authoritative DNS. We would like to move away from that. We added dnsnode in-zone. We should add at least a second provider, and then retire our hosts. Then, we should update the delegation(s) in the parent(s).
dnsnode provides anycasted authoritative DNS, from many locations. Besides making it hard to kick our names off the internet by dosing our silly servers, users need to traverse a lesser part of the internet in order to reach DNS data for us.
We want another one like dnsnode before we shut down our own servers.
so i know about all this, and i want a poney too. :) the question is more "why". the brussels notes and this ticket don't say why we want to stop running our own DNS servers clearly.