we are managing our DNS data at Azure DNS. They provide 4 NS for redundancy, but just two days ago the whole Azure DNS service went down for a few hours, and all of our services with it as well. Now i'm looking for a better redundancy for such a worst case scenario.
Unfortunately Azure DNS does not support outgoing zone transfer to a secondary NS hosted by a different provider. But they provide a tool for exporting all data of a zone into a zone file.
Amazon Route 53 gives me the option, to import such a zone file. But for this i have to recreate that zone for my domain at Amazon first. And this leads to a different SOA record (and also 4 different NS entries).
My plan was to use both services (Azure and Amazon), and take from both two NS:
- MyDomain NS1 -> Azure
- MyDomain NS2 -> Amazon
- MyDomain NS3 -> Azure
- MyDomain NS4 -> Amazon
As i synchronize the zone data between the 2 providers over export / import by myself, i don't see a problem in terms of accurate DNS data. But the SOA and the NS records for the domain are not consistent.
What are the implications in such a szenario? Could that lead to problems with spam prevention or other services, who query DNS data for a domain?
Thank you in advance.