Likelihood to Recommend
Amazon CloudFront is the perfect solution for any type of company. If a company is small or medium size, CloudFront offers 1 TB monthly free bandwidth which is more than for any small and medium size companies. If we compare the speed of CloudFront with other CDN, CloudFront is way ahead of their competitors and with 1 TB free bandwidth. If someone is ready to invest time in CloudFront documentation then he/she definitely go for it.
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 if a website’s static data are based in New York City, people in Boston will get the content faster than people in San Francisco or Tokyo. The farther away customers are from a company’s data center, the slower the website or application loads. This problem can be fixed with a content delivery network like Amazon CloudFront When a visitor requests a file from your website, Amazon CloudFront automatically sends the request to a copy of the file at the nearest edge location. This results in faster download times. You may have great hosting but it doesn’t have the capacity or scalability offered by Google, Microsoft or Yahoo. The better CDNs like Amazon CloudFront offer higher availability, lower network latency and lower packet loss. Amazon CloudFront provides 24/7 email and phone support Amazon CloudFront Free Tier allows you to free up to 50 GB of data transfer and 2,000,000 HTTP and HTTPS requests / month for one year. 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 Kinda of costlier when compared to rivals providing the same service The setup of Distribution is kinda little complicated, need good exposure before setting up the service Sometimes we can go with S3 Delivery service rather than Cloudfront if the website is providing static content and its way cheaper 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
Easy way to integrate a CDN within the AWS infrastructure. It allows further customization based on company needs.
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
CloudFront is a good CDN solution. It can be a bit complicated to implement depending on your needs, but AWS tech support is great. You get to avoid a ton of upfront costs by going with CloudFront. It works best in conjunction with other AWS services in your infrastructure. Once you set it up, you won't need to do much to maintain it. It just works.
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 has always been creative and leading, and I have been using its services for years. They are very reassuring and have fast and responsive support--you can call them from any time zone to respond quickly. High security on servers, open hands on changes, and increasing and decreasing server resources and features.
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 RoI for using CloudFront is immense. You can use it for all your certificate management and static asset management of your websites using CloudFront. It is as good or better than any other CDN provider with multi-region support across the world using AWS regions. 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