I’m getting started with spaces and am trying to use spaces.company.com
as the subdomain for caching, but it’s telling me there isn’t a domain with Digital Ocean namespaces set up.
I’m assuming this means the ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
namespace records haven’t been configured, which they haven’t. The problem is when I set those records up I lose access to my Webflow site, which is what is displayed when I go to company.com
.
I want to keep it so that the Webflow site is displayed when I go to company.com
but I need the subdomain spaces.company.com
to be for my Digital Ocean Spaces. Is there a way to get a certificate for the subdomain without adding the three Digital Ocean namespace records to the site? Like I said, when I do that I’m not able to access the frontend website.
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.
Hi there,
Yes this should doable, what you could do is rather than changing your name servers, you could add NS records for your subdomain.
To do so head over to your current active DNS zone and add the following:
spaces.company.com
- NS record ->ns1.digitalocean.com
spaces.company.com
- NS record ->ns2.digitalocean.com
spaces.company.com
- NS record ->ns3.digitalocean.com
Then add the
spaces.company.com
subdomain as an actual domain under your DigitalOcean account.That way you will be able to manage the DNS zone for that subdomain name via DigitalOcean, and your main domain name’s DNS zone would remain where it is currently.
Let me know how it goes.
Best,
Bobby