The reason that Netlify DNS won’t work for this domain name is because the of the unusual behavior for the .name
top-level domain.
For most domains the root/apex domain is the first segments of the domain name, the top-level domain (TLD) and one level beneath it. Here are two examples:
example.com
:
- the TLD is
com
- the apex/root domain is
example.com
-
www.example.com
is the www
subdomain of the apex/root domain
mit.edu
:
- the TLD is
edu
- the apex/root domain is
mit.edu
-
web.mit.edu
is the web
subdomain of the apex/root domain
However, for the .name
TLD, the second and third level both must be included to get the actual apex/root domain.
chuck.martin.name
:
- the TLD is
name
- the apex/root domain is
chuck.martin.name
-
www.chuck.martin.name
is the www subdomain of the apex/root domain
Netlify DNS doesn’t support the “include two levels beneath the TLD” behavior which is why the .name
domains cannot use Netlify DNS at this time.
The DNS records themselves are typically created in a DNS settings page for the domain at the domain registrar. For this domain, I’m showing the registrar is Domain.com.
If you can make a CNAME record for the apex/root domain, please do so. However, CNAMEs are not allowed on the apex/root domain in most cases. (If it is allowed by your DNS service the is often called something different like an ALIAS type record).
If you can use a CNAME for the apex/root domain, please do so. If this is not supported by the DNS service then use an A record pointing to 104.198.14.52 for the apex/root domain and a CNAME record for any/all subdomains of the apex/root domain.
For example:
chuck.martin.name. 900 IN A 143.95.80.138
www.chuck.martin.name. 900 IN CNAME subdomain.netlify.com
Or, if CNAMEs on the apex/root domain are supported, this:
chuck.martin.name. 900 IN CNAME subdomain.netlify.com
www.chuck.martin.name. 900 IN CNAME subdomain.netlify.com
For the actual record, you will replace the subdomain.netlify.com
with the real subdomain under netlify.com
for your site.
Regarding adding this information to our public docs, I’d be happy to discuss this with our docs team. We walk a difficult line between including all information and keeping the docs short enough that people will read them completely. While a more verbose doc might be helpful for some people, as the docs become more detailed there is an increase people not reading or only partially reading those docs.
If adding all that to our docs isn’t feasible, what do you think about us creating one of our “common issue topics” here in community? Would adding the explanation above regarding TLDs, apex/root domains and subdomains in a “common issue” community topic instead? We could then include a link to that page on the docs page if additional explanation and/or examples would be helpful for readers there.
Please reply anytime if there are other questions and/or share preferences regarding a docs update vs a community common issue topic.