Likelihood to Recommend Google cloud is well suited to access and collaborate on documents where more than 2 people are required to contribute and in instances where feedback from individuals is captured on the document itself. If a team is working on an end of year report for funders, a few key members may need to finalise a report by offering suggestions that can be viewed and resolved by other team members. Housing documents on Google Cloud is the most appropriate platform I have ever used for tasks like these. If minimal collaboration needs engagement from just 2 individuals, it may be easier to simply email the information between each other, rather than using time to create a folder, ensure access control and upload the information to Google Cloud for collaborative input
Read full review 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.
Read full review Pros Interface is user friendly It is safe , Secure and reliable It has lower pricing plans They have good customer support They do have good documentation to have fair ideas on their offerings Read full review The portal management is very easy to use in comparison to other companies for DNS management. The have expert mode that allows for multiple edits on records and allows you to make notes for each edit on a zone. The have TTLs that are as low as 30 seconds. Read full review Cons It is hard for first time user to get used to it. Support is restricted for 3rd party services who uses it Sometimes the support people take more than 24hrs to reply to our queries, But it is not for all issues. Search function could have been made easy to search records Read full review Simpler billing interface 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. Read full review Likelihood to Renew It does exactly what we need, its fast, secure and reliable.
Read full review Usability This is exceptionally simple to utilize in the event that you are as of now utilizing Google Cloud Services or you are important for the Google Ecosystem as of now. I accept this is likely the primary goal of Google Cloud DNS, to give a more complete set-up of devices to Google Cloud clients. Consequently, I would rate convenience a 9.
Read full review 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.
Read full review Support Rating In the event that you are utilizing Google Cloud Platform as your cloud supplier, Google Cloud DNS is unquestionably the DNS supplier to utilize.
I haven't required help for it yet, notwithstanding, in my experience, Google Support is incredible.
Read full review 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
Read full review Alternatives Considered Amazon Route 53 offers almost equal or slightly more features than Google Cloud DNS; we selected Google Cloud DNS because the rest of our projects use Google Cloud Platform.
Also, since AWS is a bigger service provider, their pricing is also higher; since Google Cloud DNS pricing is better, we went for it.
Read full review 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.
Read full review Return on Investment We use GCP for all our projects so Google Cloud DNS fits perfectly It is proving to scale well so good for us since we are a growing company It is easy to use and doesn't require a separate team to maintain Read full review 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. Read full review ScreenShots