4 ms·
> The problem stems from the fact that the DNS specification dates from 1987 ... As a result, the DNS spec enshrined that the root record -- the naked domain wi
by mindslight 13y ago
> The problem stems from the fact that the DNS specification dates from 1987 ... As a result, the DNS spec enshrined that the root record -- the naked domain without any subdomain -- could not be a CNAME
This isn't due to a lack of foresight in the spec, but people's misunderstanding of what a CNAME record actually means. A CNAME says that this name refers to the exact same thing as another name, including all subnames.
You can CNAME the "bare" example.com to foo.example.org, but it would involve getting the .com nameservers serve that record instead of NS records. By having NS and SOA records for example.com, you can no longer say that the two names are equivalent. Rather than having to define a merge algorithm (eg what happens if example.com and foo.example.org both have MX records?), the RFC simply rules out additional records on the alias.
- AnthonyMouse 13y agoWhich makes me wonder what they're doing for record types other than A/AAAA. If you have "example.com. CNAME example.net." then which record does Cloudflare provide if both example.com and example.net each have an MX record, or a TXT record, etc.? Do you get the MX record from example.com if there is one and the MX record from example.net if there isn't?
- takeda 13y agoThey butchered it when allowed CNAME in the root breaking RFC and other things with it, so I would not be surprised that they don't do anything, but perhaps majority only cares about A/AAAA.