Custom Domain Error: "Already Taken" After Repo Move to New Organization

[michael-borck]

Select Topic Area

Question

Body

I am unable to re-add my custom domain to a GitHub Pages site after moving its repository to a new organization.

The Problem

I recently moved my repository from michael-borck/michaelborck.educaiton to michaelborck-website/michaelborck.education.

The custom domain michaelborck.education was working correctly before this move.

After the move, the site now shows a 404 error: "There isn't a GitHub pages site here."

When I go to the new repository's settings (michaelborck-website/michaelborck.education > Settings > Pages) to add the custom domain, I receive this error:

The custom domain michaelborck.education is already taken. If you are the owner of this domain, check out [GitHub Docs link] for information about how to verify and release this domain.

What I've Checked

• DNS Settings: My DNS is configured correctly. It is an apex domain with the required A records pointing to GitHub's IPs, per the documentation. This exact setup was working before the move.

• Verification: I have followed the verification steps, but the error persists, suggesting the domain is locked to the previous repository location.

• Comparison Case: I have an identical setup for michaelborck.dev (same DNS provider, similar DNS records) linked to a different repository. I also moved that repository to the new organization at the same time, and it is working perfectly.

It seems the michaelborck.education domain is "stuck" in GitHub's system and is still associated with the old, pre-move repository.

Could someone please assist in manually releasing this domain so I can add it to my new repository?

Domain: michaelborck.education

New Repository: michaelborck-website/michaelborck.education

[JeanCarlos88]

Hi Michael,
This issue is fairly common when moving repositories with custom domains on GitHub Pages. Here's how you can resolve it:

• Check if the domain is still linked to the old repository. Even after moving the repo, GitHub may retain the domain association. Go to the old repo (michael-borck/michaelborck.education) and remove the custom domain from the Pages settings.
• Clear the CNAME file in the old repo. If this file still exists, it may hold the domain binding. Delete it or confirm it’s removed.
• Wait for propagation. After removing the domain, GitHub may take a few minutes to release it for reuse.
• Double-check your DNS records. Although you’ve confirmed they’re correct, ensure the A records point to GitHub’s IPs: 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153.
• Use domain verification. If the domain remains locked, follow the steps in GitHub’s official Pages documentation to verify ownership and release it.
  If the issue persists after these steps, you may need to contact GitHub Support to manually release the domain.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬