Cloudflare vs. Oracle Dyn Managed DNS

Based on my experience, Cloudflare is well-suited for high-traffic websites and probably e-commerce platforms. Cloudflare can mitigate the risk of attacks on these websites using WAF and DNS protection mechanisms and provide cached content to the end-users quickly. The websites where it is not suitable are those that need high security and compliance requirements as Cloudflare might not meet all those criteria.

Incentivized

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.

Incentivized

• Registrar and DNS services are impeccable, with registrations done at cost and without ADs. DNS services setting standards for speed of resolution.
• DDOS protection. With their content distribution network to back them they have the bandwidth and tools to be both proactive and reactive to bad actors.
• WAF - Their Web Application Firewall helps mitigate common site vulnerabilities and has active zero-day protection running for breaking exploits

Incentivized

• 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.

Incentivized

• In some cases, using Cloudflare can actually lead to slower website speeds if the network is congested or if the website's traffic is particularly heavy.
• Some website owners may find that the level of customization offered by Cloudflare is limited, especially in comparison to other solutions.
• While Cloudflare is easy to set up and manage, it may be too complex for users who are not familiar with web technologies.

Incentivized

• 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.

Incentivized

lower cost

Incentivized

It does exactly what we need, its fast, secure and reliable.

Incentivized

Everything is extremely concise and all settings apply immediately and take effect globally. There is no reason to explicitly plan/think in terms of individual regions as one would have to traditional cloud offerings (AWS, OCI, Azure). All Cloudflare products integrate seamless as part of a single pipeline that executes from request to response.

Incentivized

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.

Incentivized

In 6+ years of relying on Cloudflare, I think we experienced one or two brief outages that were Cloudflare's fault.

Incentivized

Their Argo for the global network is the core feature we love.

Incentivized

I have only used their support a few times, and most times, they are responsive and able to resolve my issue with a minimal amount of time and effort. However, there was one instance where I simply asked about how to purchase some more resources (redirect rules), and I received some type of automated/AI response that was very unhelpful and gave me no opportunity to escalate to a person.

Incentivized

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

Incentivized

Very well executed implementation where our team was able to handle the implementation with guidance.

Incentivized

Firebase can be a good starter for basic projects but as I scaled up, I found it lacking the maturity Cloudflare has. Naturaly, I opted for Cloudflare for bigger projects. I still use Firebase, but for small scale hobby projects only.

Incentivized

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.

Incentivized

They are built for scale and have the capacity to handle all the traffic we could ever expect to get.

Incentivized

• A lot of requests are cached and so egress costs from downstream providers are mitigated.
• DDoS protection has also managed to keep our site up and our cloud computing bill down.
• Setting up a proxy with a worker made putting various Google Cloud Functions running behind a single URL very easy and performant. Plus they offer API Shield on top of this.

• 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.

Incentivized