Report this

What is the reason for this report?

Using digital ocean DNS to point to another NS

Posted on September 28, 2014

I have a large amount of clients that have their DNS pointing to ns1.digitalocean.com / ns2.digitalocean.com / ns3.digitalocean.com.

Is there any downside of changing the NS in digitalocean to point to cloudflare’s nameservers??



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

some of our clients have their domains registered elsewhere and cannot access their accounts to change NS. as long as there is no negative affects by using DO’s DNS Manager to point to cloudflare then that is all I need. Thanks asb.

Replacing DigitalOcean’s NS records with CloudFlare’s in the DigitalOcean DNS manager shouldn’t cause any issues. Though unless I’m missing something, it sounds like using DigitalOcean’s DNS manager is an unnecessary step. We simply proved the tools to manage DNS from our control panel as a convenience. There is no requirement to use it. If you’re going to manage DNS through CloudFlare, you could simply skip using the DigitalOcean DNS manager all together and add their NS records in the domain registrar’s panel.

If you could add some more context, we might be able to help you better.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.