I created these two DNS records:
ALIAS statusok.com statusok.netlify.com CNAME www.statusok.com statusok.netlify.com
When a user requests the subdomain
- her browser receives a
CNAMEto look up
- her browser looks up
- her browser receives an
Arecord from Netlify's pool of available CDN nodes geographically closest to the end user
% dig www.statusok.com ;; ANSWER SECTION: www.statusok.com. CNAME statusok.netlify.com. statusok.netlify.com. A 220.127.116.11 ;; AUTHORITY SECTION: netlify.com. NS ns1.p04.nsone.net. netlify.com. NS ns4.p04.nsone.net. netlify.com. NS ns2.p04.nsone.net. netlify.com. NS ns3.p04.nsone.net. netlify.com. NS s1.netlify.com.
If Netlify detects their main load balancer is slow or unresponsive (for example, if under a DDoS attack), they route around that on the DNS level.
When a user requests the apex domain
ALIASrecord sends a
CNAMElook up to Netlify at
- her browser receives an A record from Netlify's pool of available CDN nodes geographically closest to the end user
% dig statusok.com ;; ANSWER SECTION: statusok.com. A 18.104.22.168 ;; AUTHORITY SECTION: statusok.com. NS ns4.dnsimple.com. statusok.com. NS ns3.dnsimple.com. statusok.com. NS ns2.dnsimple.com. statusok.com. NS ns1.dnsimple.com.
Netlify can still route around outages. End users save an extra DNS lookup.
ALIAS record is better for this case
A record or
URL record on DNSimple.
A record doesn't let Netlify insert traffic direction between
the end user's DNS lookup and Netlify infrastructure.
So, they can't route users to the closest CDN node or around an outage.
URL record is a 301 redirect,
which doesn't support https.
https://www.statusok.com would work
https://statusok.com would not.