done

[hyunnkim]

]

[Radi410]

this usually happens because of a 'stale' internal routing record that gets stuck when a repo toggles between public and private.

Even though your DNS and TXT records are perfect, GitHub’s backend still thinks the domain is 'claimed' by the previous state of that repository. To force a refresh of the routing table, try these steps in order:

The 'Kick' Method: Go to your repository settings for hyunnkim/frontpage, go to the Pages tab, and temporarily change the Source from 'Deploy from a branch' to 'GitHub Actions' (or vice versa). Save it, wait 30 seconds, and switch it back. This often forces the domain availability check to re-run.

Remove and Re-add: If you can see the domain in the 'Custom Domain' field (even with an error), delete it entirely, click Save, wait a minute, and then type williamkim.net back in.

Check Organization/User Settings: Navigate to your User Settings > Pages. Sometimes a domain gets 'Verified' at the account level but is stuck in a 'Pending' state for a specific repository. Ensure williamkim.net is listed and verified there.

Note to GitHub Support: Since it has provided a valid _github-pages-challenge TXT record, if the steps above don't work, a staff member can manually purge the stale entry from the global routing table.

[hyunnkim]

You fixed it! Thank you so much!

[Radi410]

no problem. Trying to get my community achievement. Could you mark it as solved for me?