[stephenr]

The solution here is one for customers, not providers.

Manage your DNS at one location on "master" (potentially a "private" server with IP restricted access and zone transfer ACLs).

Setup 2+ accounts with "DNS providers" that support incoming zone transfers - that is, they can operate as "slave" DNS servers, pulling records automatically from your "master" (once access rules are set of course) and returning results directly to clients making DNS queries.

Most "Secondary DNS" packages are < $50 year, so use a few, and don't worry about individual DNS networks being burnt to the ground.

[jhealy]

It seems like inbound and outbound zone transfers aren't offered by a number of providers (like AWS). Do you know of a list of DNS providers that support either option?

[mike-cardwell]

I used to use these two services together do this:

  https://puck.nether.net/dns
  https://acc.rollernet.us/

They're both free to sign up, provide free secondary DNS, zone transfers and fully support IPv6.

I only stopped using them because I wanted to run my own DNS service.

[JonahBraun]

EasyDNS provides integration with AWS: http://easyroute53.com/

They have an interesting blog post about setting up secondary DNS: http://blog.easydns.org/2013/09/10/what-we-are-doing-about-c...

I have no affiliation with them, just a happy customer.

[stephenr]

A search for "secondary DNS service" should give you several results.

My research into it is from a "manage your DNS records internally, then use a couple of providers for all public facing responders". In that situation all you need them to support is inbound transfers, which several do.