- Can an ALIAS record (without any A record) be used with an apex domain to point to the Netlify subdomain (e.g.
my-site.netlify.app), rather than pointing the apex domain to the Netlify load balancers? I am asking this for the case where we would like to keep our current external DNS provider, which is not one of the recommended providers in the Netlify docs (NS1, Cloudflare).
- If so, would this then utilize the higher Netlify CDN speeds when sending requests to the apex domain (rather than the slower CDN speed when pointing to the load balancers and having to go through a redirect to the
- Finally, would changing the Netlify primary domain to be the apex domain affect this behavior?
site name: TBD
custom domain: datascijedi.org (or www.datascijedi.org)
I am looking into using an external DNS Provider with Netlify web hosting. I read in the Netlify docs that the recommended setup is to use (1)
www as the Netlify primary domain, (2) a CNAME for the
www subdomain pointing to the Netlify subdomain, and (3) an ANAME, ALIAS, Flattened CNAME, or A record for the apex domain pointing to the Netlify load balancers. The docs also suggest that the
www subdomain should be set as the Netlfy primary domain to take advantage of Netlify’s higher CDN speeds.
However, it is not clear to me why the recommendation is to use an ALIAS record to point the apex domain to the Netlify load balancers, rather than directly to the Netlify subdomain, and what the CDN speed implication of this might be. This has implications on preferring use of the apex domain or a
www subdomain, so any thoughts on this would be very helpful.
Thank you in advance. a