Custom domain issue when recreating repo

[stark0de]

Select Topic Area

Question

Body

Hi all, I seem to have an issue with setting up a custom domain. I previously had a Github Pages blog setup in stark0de.github.io and the domain stark0de.com pointing to it correctly. Because I wanted to make some changes I deleted the repo and re-created it with new content (it is using Hugo to deploy the site with Github Actions). I tried to configure the custom domain from Settings>Pages but I got the following error message: The custom domain stark0de.com is already taken. If you are the owner of this domain, check out https://docs.github.com/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages for information about how to verify and release this domain. The new blog was deployed correctly to stark0de.github.io but it seems that I cannot remove the association to the previous repo (right now stark0de.com points to a blank github pages site). Any help would be appreciated! Thank you.

[gebz123]

This happens because GitHub “locks” a custom domain to stop takeovers.

Do this:

1. Make sure the domain isn’t still set somewhere else

• Check any old repo/org Pages settings.
• Remove the custom domain there.
• Also delete any CNAME file in the old Pages branch (if it exists).

2. Verify you own the domain (this is the real fix)

• Go to your repo → Settings → Pages.
• Add the custom domain.
• GitHub will ask you to add a TXT record like:
  • _github-pages-challenge-<your-user-or-org> = <value GitHub gives you>
• Wait for DNS to propagate (can take minutes, sometimes hours).
• Hit Verify again.

3. Point DNS to the new Pages site

• If you use www.stark0de.com: set a CNAME to stark0de.github.io
• If you use stark0de.com (apex): use GitHub Pages A records (per GitHub docs)

After verification + correct DNS, the “already taken” error goes away and the domain attaches to the new repo.

Hope this helps.

[stark0de]

The verification worked, thank you! :)

[Ayla-hmadi]

Hi there!

This is a common issue when you delete a GitHub Pages repository that had a custom domain configured. The domain remains "claimed" by the old (now deleted) repository, preventing you from using it with your new repo.

Solution: Verify Your Domain Ownership

You need to verify domain ownership to release it from the old repo. Here's how:

Step 1: Add DNS TXT Record for Verification

1. Go to your GitHub account settings (not repository settings): https://github.com/settings/pages
2. Under "Verified domains", click "Add a domain"
3. Enter stark0de.com
4. GitHub will provide you with a TXT record to add to your DNS

The TXT record will look something like:

_github-pages-challenge-stark0de.stark0de.com TXT "verification-code-here"

5. Add this TXT record in your domain registrar's DNS settings
6. Wait for DNS propagation (can take a few minutes to 24 hours)
7. Click "Verify" in GitHub settings

Step 2: Configure Custom Domain in New Repo

Once verified:

1. Go to your new repository: stark0de/stark0de.github.io
2. Navigate to Settings > Pages
3. Under "Custom domain", enter stark0de.com
4. Click Save
5. Enable "Enforce HTTPS" once DNS propagates

Alternative Quick Fix (If Verification Doesn't Work)

If domain verification is taking too long or not working:

1. Temporarily remove the CNAME record from your DNS that points to stark0de.github.io
2. Wait ~1 hour for DNS propagation
3. Try adding the custom domain again in your new repo's Settings > Pages
4. Re-add the CNAME record once configured

Your DNS Configuration Should Be:

Type: CNAME
Name: www (or @)
Value: stark0de.github.io

Or for apex domain:

Type: A
Name: @
Value: 185.199.108.153
       185.199.109.153
       185.199.110.153
       185.199.111.153

Additional Tip

In your Hugo repository, make sure you have a CNAME file in your static/ directory containing:

stark0de.com

This ensures the custom domain setting persists after deployments.

---

The domain verification method is the most reliable solution. Let me know if you encounter any issues!

[stark0de]

The domain verification solved it, many thanks :)