In my experience Dyn pushes this functionality very hard during customer on boarding, effectively as a lock in for their platform.
Re:Massive Dyn DNS outage
by mancerayder on Friday October 21, 2016 @01:32PM
(#12762569)
Well I really think those features are useful, though. They let you get some powerful de-facto load balancing and HA and other complex 'features' without any new hardware or much complexity. They give you some easy creative freedom in designing a redundant infrastructure, give you some geo-aware DNS the likes of which I remember paying Akamai a lot of money for years go, etc. But the lock-in problem is absolutely right.
I'm also familiar with the aggressiveness of that sales team. I prefer another provider and they were trying to solicit our business by specifically calling out our provider as amenable to a DDOS attack which had occurred.
Someone with a simpler setup with standard DNS features will find it much easier to use multiple providers, of course.
EDIT: joking aside, the issue with multiple DNS providers is primarily (in my experience at the company I'm at having investigated this in the past) intelligent DNS entries. Example, 'return these A records, in this order, based on the number of requests, roughly balanced'.
There's no universal standard, just common aspects. DNS Provider A has one set of features, names for returning A records in some way, based on some weighted averaging, provider B has a different mechanism. So as an infrastructure person you have to:
1. Investigate provider A and B features for intelligent DNS (it's not even universally called intelligent DNS!), and mentally parse the commonalities and differences
2. Create a custom mechanism to keep them in sync internally. So you hope that A and B have an API for maintaining the records.
3. Ensure that when someone in your org wants to make an update, A and B update at the same time in the same way
4. APIs don't change.