3 ms·
One reason is that you "can't" CNAME your apex domain. So redirecting foo.com to www.foo.com might give you a little more deployment flexibility. The servers ho
by grogers 6y ago
One reason is that you "can't" CNAME your apex domain. So redirecting foo.com to www.foo.com might give you a little more deployment flexibility. The servers hosting the redirect don't need to be super beefy like your main site so just a A/AAAA might not lose you much.
Just a guess.
- hug 6y agoThere should be no scare quotes around can’t. CNAMEs on the apex don’t exist because CNAMEs are not allowed to coexist with other record types, and you can’t have an apex without NS records or SOA records or whatever else it may be. You can have a wacky DNS server that allows you to do weird things like ‘alias’ records, but those are sidestepping the DNS RFC: They’re answering with A records, but in a dynamic fashion.
- JdeBP 6y agoOf course, were WWW browsers like a lot of other softwares are, there would be a SRV lookup of the domain, plus the protocol and transport, and the deployment flexibility would be in that mechanism. (-: * http://jdebp.uk./FGA/dns-srv-record-use-by-clients.html http://jdebp.uk./FGA/dns-srv-record-use-by-clients.html Problems are more along the lines of conflicts with internal Active Directory deployment and "split horizon" DNS service. * http://jdebp.uk./FGA/web-allowing-omission-of-www.html http://jdebp.uk./FGA/web-allowing-omission-of-www.html * http://jdebp.uk./FGA/dns-split-horizon-common-server-names.html http://jdebp.uk./FGA/dns-split-horizon-common-server-names.h...