Best way to manage Global DNS versus Project DNS

I’m looking at the digital ocean DNS servers and trying to understand how to handle global dns like domain.tld versus sub.domain.tld which might be related to a project.

For example

  • Project 1: Website www/domain.tld
  • Project 2: App app.domian.tld
  • Project 3: API api.domain.tld
  • Project 4: Workers workers.domain.tld

Some of these projects will talk across project boundaries through an API or other contract. Hopefully with internal routing. Others like the website would be completely standalone.

Is it best practice to separate the domains through NS servers across projects for each subdomain and put the main domain with the website. Or should I create a DNS project just to manage DNS?

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Site Moderator
Site Moderator badge
February 14, 2023

Hey @charleschristolini,

I believe the best and easiest way is to add your Domain in your DigitalOcean’s account and manage every DNS entry from there from one place rather than having like 5-6 places where DNS is being managed.

Yes, if you have a lot of records it might get a bit harder to read however it would still be better to have it in one place rather than in multiple places. Here is an article on how to manage your DNS with DigitalOcean as well:

Hope this helps!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up