3 ms·
One reason some sites used to be stuck with this configuration is that you can CNAME a www subdomain to a CDN but you can't CNAME your eTLD+1 without also affec
by EE84M3i 2y ago
One reason some sites used to be stuck with this configuration is that you can CNAME a www subdomain to a CDN but you can't CNAME your eTLD+1 without also affecting your other records (MX/etc).
There have been various solutions to this problem like ALIAS records, but perhaps they never upgraded.