jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-23 21:07:12 -05:00
Code Issues Projects Releases Wiki Activity

Clarifying CNAME file instructions

Browse Source 
To prevent confusion around “CNAME” as a DNS term vs. “CNAME” 
as a file name, I’m using the term “domain name.”
This commit is contained in:
Vlad GURDIGA
2021-03-19 11:40:26 +02:00
committed by GitHub
parent 84fdf589a6
commit ddcde4ba89
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/github/working-with-github-pages/troubleshooting-custom-domains-and-github-pages.md
View File

@@ -23,8 +23,8 @@ Then, make sure the _CNAME_ file is formatted correctly.
- The _CNAME_ filename must be all uppercase.
- The _CNAME_ file can contain only one domain. To point multiple domains to your site, you must set up a redirect through your DNS provider.
- The _CNAME_ entry must be the bare domain. For example, `www.example.com`,`blog.example.com`, or `example.com`.
- The _CNAME_ entry can only be used once on {% data variables.product.product_name %}. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository.
- The _CNAME_ file must contain the domain name only. For example, `www.example.com`, `blog.example.com`, or `example.com`.
- The domain name must be unique across {% data variables.product.product_name %}. For example, if another repository's _CNAME_ file contains `example.com`, you cannot use `example.com` in the _CNAME_ file for your repository.
### DNS misconfiguration