Score:-1

having www.domain.com serve up content from digitalocean spaces cdn

cn flag

Say I have domain.com and I would like it to serve up static content hosted on a DigitalOcean Space.

I updated my DNS registrar (GoDaddy) to have ns1.digitalocean.com and ns2.digitalocean.com as the nameservers per https://docs.digitalocean.com/tutorials/dns-registrars/

In Networking - Domains, on digitalocean.com, I added domain.com and www.domain.com. On creation each domain had 3 NS entries:

enter image description here

I then created a DigitalOcean Space, uploaded my files and added www.domain.com as a custom subdomain:

enter image description here

Doing so added a CNAME record to the domain.com:

enter image description here

The problem is that when I visit www.domain.com or domain.com in my browser I get a "This site can't be reached" error. Doing nslookup www.domain.com yields the following:

Server:  UnKnown
Address:  192.168.1.1

Name:    www.domain.com

What do I need to do to make it so that www.domain.com is serving up content from the CDN?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.