Can you use DigitalOcean's name servers for any domain?

Question

I have a Droplet and therefore an account with DigitalOcean.

I am not yet running any website out of that Droplet.

Suppose I have a domain.

Can I

at the domain registrar site, point the domain to DigitalOcean’s name servers
and at DigitalOcean, set various (A, MX, etc.) records to direct traffic to wherever my Web, email, etc. servers are hosted?

I have looked at: https://docs.digitalocean.com/products/networking/dns/getting-started/dns-registrars/

It tells me how to point domains to DO’s name severs but does not seem to answer the question above.

The point of the question is whether I could use DO as name server for a domain that is as yet not hosted with DO and otherwise has nothing to do with DO.

Thanks.

Bobby · Accepted Answer

Hey! Absolutely, Arnold! You can indeed use DigitalOcean’s name servers for any domain, regardless of whether your website or services are hosted with DigitalOcean or not. Here’s a breakdown of how you can set this up: Point Your Domain to DigitalOcean’s Name Servers : First, at your domain registrar’s site, change the name servers for your domain to DigitalOcean’s name servers. Typically, these are: ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com This process may vary slightly depending on your registrar, but in general, you’ll find the option to change name servers in the domain management or DNS settings area. Set Up DNS Records in DigitalOcean : Once your domain is pointing to DigitalOcean’s name servers, log in to your DigitalOcean account. Here, you can add your domain and set up various DNS records (like A, MX, CNAME, etc.) according to your needs. These records will direct traffic to your web, email, and other servers, irrespective of where they are hosted. Go to the Networking section in your DigitalOcean dashboard. Add your domain under the ‘Domains’ tab. After adding your domain, you can start creating DNS records. For example, an A record can point your domain to the IP address of your web server, and MX records can direct email traffic to your email servers. Propagation Time : Remember, after making these changes, there might be a propagation period. DNS changes can take up to 48 hours to fully propagate across the internet, though it’s often much quicker. Test Your Setup : Once you’ve set up your DNS records, it’s a good idea to test and ensure everything is working as expected. You can use online tools like dig or nslookup to verify your DNS settings. In summary, DigitalOcean’s DNS service is quite flexible and can be used for domains regardless of where the actual services are hosted. It’s a great way to manage your DNS records, especially if you’re already using DigitalOcean for other services. Just keep in mind the DNS propagation times and always double-check your DNS settings for accuracy. Happy hosting! Best, Bobby

KFSys · Answer

Heya @oceandigger , Yes, you can use DigitalOcean to host your DNS here. First, regarding namerservers, you can use these: ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com Once you have changed the Nameservers of your Domain to the above, youy can add your Domain to your DigitalOcean Control Panel and start editing your DNS records. Ideally, you can do that before you change your Nameservers, configure your DNS records and after that change them.

alexdo · Answer

Hi there, Bobby’s answer above is the right way to structure your variables and config files for staging versus live. One thing worth adding before you rely on that setup: separate .env files and separate project.yml files control what gets deployed and with what values, but they do not by themselves give you two coexisting, separately callable environments. Doctl deploys into whatever functions namespace you are currently connected to, and deploying a project overwrites previously deployed functions in that namespace when the project and function names match. So if you deploy project.staging.yml and then later deploy project.live.yml into the same namespace, the second deploy replaces the first rather than the two living side by side. To actually have a live test environment and a live production environment running at the same time, you need separate namespaces: doctl serverless namespaces create --label staging --region nyc1doctl serverless namespaces create --label production --region nyc1 Then connect to whichever one you are deploying to before running serverless deploy: doctl serverless connect production Each namespace gets its own functions and its own public URLs, so staging and production can both be live and invocable at the same time, with the env file and project.yml approach Bobby described controlling what values each one uses. Regards

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

Can you use DigitalOcean's name servers for any domain?

Related questions

DNS problem on one site today

new DNS issue today on a website, no changes for many years

Change DNS server on Ubuntu 24

Create a DNS TXT record with multiple lines?

Getting App Platform to resolve custom domains faster

App Platform: Set subdomain to redirect to folder on main domain

Why is CloudFlare blocking my website IP on App Platform?

update DO-DNS records with droplet IP

How to set up Cloudflare load balancer with DigitalOcean Application

bug or feature? API was able to create a new record even though API token does not have create permision

Domain added to DNS but nameservers return NXDOMAIN - appears to be negative cache issue

Domain added to DNS but nameservers return NXDOMAIN - appears to be negative cache issue

Report this

Can you use DigitalOcean's name servers for any domain?

Related questions

DNS problem on one site today

new DNS issue today on a website, no changes for many years

Change DNS server on Ubuntu 24

Create a DNS TXT record with multiple lines?

Getting App Platform to resolve custom domains faster

App Platform: Set subdomain to redirect to folder on main domain

Why is CloudFlare blocking my website IP on App Platform?

update DO-DNS records with droplet IP

How to set up Cloudflare load balancer with DigitalOcean Application

bug or feature? API was able to create a new record even though API token does not have create permision

Domain added to DNS but nameservers return NXDOMAIN - appears to be negative cache issue

Domain added to DNS but nameservers return NXDOMAIN - appears to be negative cache issue