GitHub Community
The CNAME is already taken #22188
-
|
I used to have a repo for a static web site years ago. Directed custom domain to it, all worked fine. After a while I deleted that repo. Few years later (now) I created a new repo, under an Organization, to publish a static web site for that domain again. Error appears: “The CNAME … is already taken” Tried removing the CNAME file from my new repo. The site got published under its Restored the CNAME file — the error is back, and the naked Custom domain displays 404 again. Please advice, who can I contact to ask to remove the “stuck” cname record from GitHub internals. Or maybe I should create a new repo with the same name as the initial one that was deleted? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi @sergiks, welcome to the GitHub Support Community! This error usually happens when your custom domain has been attached to someone else’s Pages site in error, or the previous owner of this domain used it to host a Pages site before it was bought by you. You’ll need to reach out to the GitHub Support team for direct private help with this as it will require adding a verification code as a DNS record to your domain to prove your ownership. Make sure to include the domain you’re attempting to attach to your Pages site in the message so they can help you quickly. You should be able to send a message to the support team at the following link and choose the “Help with a Pages domain or HTTPS certificate” option: GitHub Support |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Indeed, this helped. I opened a support ticket, they promptly responded. I had to verify domain ownership by adding a TXT DNS record provided, and in a matter of 1 hour the CNAME was released and my new Pages repo was working with my custom domain. Case closed ) Thanks for support! |
Beta Was this translation helpful? Give feedback.
Hi @sergiks, welcome to the GitHub Support Community! This error usually happens when your custom domain has been attached to someone else’s Pages site in error, or the previous owner of this domain used it to host a Pages site before it was bought by you.
You’ll need to reach out to the GitHub Support team for direct private help with this as it will require adding a verification code as a DNS record to your domain to prove your ownership. Make sure to include the domain you’re attempting to attach to your Pages site in the message so they can help you quickly. You should be able to send a message to the support team at the following link and choose the “Help with a Pages domain or HTTPS…