NameCheap subdomain doesn't point to a DigitalOcean Droplet

Hey!

This actually looks all correct, when did you make that change? Usually, it can take up to 24 hours for the DNS cache to clear over the Globe before you can see the actual changes.

Do you get the correct records back when using a DNS lookup tool like this one here:

https://www.digitalocean.com/community/tools/dns

Besides that, the way that you’ve got this setup is correct where you now should be able to manage your DNS records for your subdomain via your DigitalOcean account. But a simpler setup for subdomains is usually to just add an A record for your subdomain to point to the IP address of your server. There should be no need to add NS records and to add the domain under your DigitalOcean account.

Adding just the A record under your NameCheap account is enough. You would usually add the NS records and add the subdomain under DigitalOcean if you wanted to manage more DNS settings for that specific domain via your DigitalOcean DNS zone.

Let me know how it goes with the DNS propagation and if it has been more than 24 hours, I could suggest removing the subdomain from your DigitalOcean account, deleting the subdomain NS DNS records, and only managing the A record for the subdomain via the NameCheap DNS zone.

Best,

Bobby

Heya @neonloneliness,

Just so that I get it straight, you made your nameservers to be DigitalOcean onaces and started managing the DNS from DigitalOcean is that correct?

For that to work you’ll need to make your nameservers

• ns1.digitalocean.com
• ns2.digitalocean.com
• ns3.digitalocean.com

where your Domain is being managed by(most probably from where you bought it), in this case probably Namecheap. Then your DNS will work.

Heya, @neonloneliness

I’ll also recommend to check the DNS records using our DNS lookup tool and ensure they’re correct.

https://www.digitalocean.com/community/tools/dns

Also as mentioned the DNS propagation might take up to 24 hours due to DNS cache from ISPs and also local DNS cache is a factor when it comes to updating DNS records. You can always flush local DNS cache to ensure the problem is not happening on your local device.

Regards