The Google Cloud CDN is touted as a low cost option with tight integration with Google Cloud apps and services.
N/A
Oracle Dyn Managed DNS
Score 8.8 out of 10
Mid-Size Companies (51-1,000 employees)
Oracle Dyn DNS (domain name system) is an infrastructure-as-a-service that is touted by Oracle Dyne as one of the highest performance global networks existent. It is available as a managed DNS with secondary DNS available for more reliable business continuity on higher service tiers.
Google Cloud CDN is available globally and supports various load balancers available in different regions around the globe, so I find Google Cloud CDN as one of the best choices for CDN as it serves globally and it is really fast, safe, and secure. It might be not suitable for you if you do not have any technical background.
Oracle managed DNS becomes very heavy when there is an ample amount of DNS being managed. However, the DNS creation and updating takes very less time to propagate and is very easy to use. So, for an organization, where there is a modest amount of DNS to manage, it works very well and gives a splendid experience. So, considering the complexity of managing the DNS for an IT company Oracle Dyn managed DNS is the best option to opt.
The intelligent categorization and management of site content cache in Google Cloud CDN is unique and offers the best results with simple settings.
It has powerful servers in all geographical regions of the world and the speed of the site will increase many times for the customer with smart routing.
It has AnyCast IP feature and website receives a single global IP address. In this case, the site loads at the same speed worldwide.
More responsive sales team to provide relevant QBRs to ensure proper and best practice use of the product/platform
Integration of the Dyn ECT Managed DNS with Dyn Domain Registration would be a nice feature as currently I have to manage two consoles and billing accounts.
This is the only real gripe we have with Dyn; their web-UI can be remarkably painful to use. In the "simple" editor, DNS records are arranged in a kind of "node" view, where each record is a node and any records of the same name or longer (i.e. all records called "record.example.com" or "other.record.example.com") fall under it. This creates an odd sort of hierarchical view that's not really representative of the zone file. The "expert" editor doesn't have an actual delete button, just a checkbox. If you want to update conflicting record types (for example, replacing an A record with a CNAME) you have to check the box for the record being deleted, save changes, create the new record, save changes, and finally publish changes. Dyn uses a publish model for changes, where all changes you make are staged and can be reverted or published all at once. This is fine, except that the publish/revert dialog is in a different page. This is nice when you have many changes, but very annoying when you're changing just one or two records across multiple zones. These are relatively minor issues in an otherwise good platform; annoyances more than deal breakers.
I didn't have the need to use support from Google when I was either testing or setting up my website. Information was easily found by searching online if I needed to, and the options that I needed to install or enable were there on the setup page. Honestly, I was a former systems administrator so most of this stuff is not challenging for me.
The support team at Dyn has always been very helpful and have tried to answer our questions to the best of their knowledge. We have never had any issues from support tickets and they are often resolved in a few hours
We have limited software developers and don't have the need for a big cloud service provider along with their costs. Google Cloud CDN brings to usr, reliability and brand familiarity. Google Cloud CDN also doesn't bother us with pitches or 1000 emails about the products. We went and signed up for it, without dealing with a pushy salesperson.
We use both Oracle Dyn Managed DNS and Amazon Route 53. We like having our main DNS provider outside our cloud provider in case there's an issue with Amazon and we need to point things somewhere else temporarily. But for all the smaller stuff and internal stuff, we use Route 53 successfully.
For the law firm its being used for, it keeps their remote users working. For law firms, time is money, usually every 15 minutes lost can be a big deal to them.
Sometimes it has switched when its not supposed to, and causes downtime. No real way to inform users when the switch is happening, it would be great to have an email alert we can not only send to ourselves but a notification to primary and technical partners in the firm so they don't have to yell at us like something is broken, instead they are aware it had to change.
