Overall Satisfaction with Oracle Dyn Managed DNS
We use Dyn to manage our domains and subdomains in order to send mails and route our different sub-domains to our apps. It's currently operated by the infrastructure team only, developers don't have to worry about it with some exceptions.
- Easy to navigate. You select a zone and there you have a tree containing all the sub-domains in that zone; sub-sub-domains are grouped with their sub-domain and you can expand them just clicking.
- Not error prone. You make the changes and then you publish them, minimizing the risk of changing something for mistake.
- Average HTTP API.
- API calls (i.e. from terraform) sometimes fail under certain circumstances. The API is good but not flexible enough to have it all automatized.
- UI is strange sometimes, for example, yesterday I was trying to change the TTL of a TXT record in our root domain and changing its TTL *sometimes* changed the TTL of all the TXT records under that domain (there were two), sometimes not. This was using the Simple Editor.
- As we never had any problems with Dyn, I think [there is a] neutral impact, because if it's working, the impact is done by other parts of our product.