I’d prefer to use Netlify DNS but I’m not sure how to accomplish the subdomains to be pointed to different production deploys.
If that’s not possible, then I can just use Namecheap’s DNS and point CNAMEs to each deploy.
Hope that’s making sense.
Ok, reading further, it looks like the subdomains will have to be a CNAME from namecheap’s DNS to specific netlify deploys.
I’m confused about what to do for the apex domain if I’m using CNAMEs for the subdomains. Namecheap does allow ALIAS.
If you want to use Netlify DNS and point subdomains to different production deploys, you have a couple of options. Netlify DNS supports records like A, AAAA, CNAME, and TXT.
To point subdomains to different production deploys using Netlify DNS, you can create individual A or AAAA records for each subdomain and set their respective IP addresses. For example:
subdomain1.example.com. A 192.0.2.1
subdomain2.example.com. A 192.0.2.2
If you prefer to use Namecheap’s DNS and point CNAMEs to each deploy, you can do so as well. In this case, you would create CNAME records for each subdomain and set them to the Netlify subdomain URLs. For example:
You can use Netlify’s deploys for your subdomains while still using Namecheap for your DNS management.
Regarding the apex domain (e.g., example.com) when using CNAMEs for the subdomains, Namecheap does not allow CNAME records at the apex domain. According to Namecheap’s documentation, they offer ALIAS that can be used as an alternative. From my understanding ALIAS acts similarly to a CNAME but is allowed at the apex domain.
You can create an ALIAS record for your apex domain and set it to the Netlify subdomain URL for your main deploy. This way, requests to the apex domain will be properly directed to your Netlify deploy.