Add CNAME file for GitHub Pages custom domain (openkline.tech)#14
Merged
Conversation
GitHub Pages requires a CNAME file in the publishing source to claim and serve a custom domain. Without it the domain health check reports NotServedByPagesError.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The GitHub Pages custom domain health check is failing for
openkline.tech:I checked the live DNS and most of it is actually correct, so the failure comes down to two things — one of which is fixed here.
Live DNS state
openkline.techA185.199.108–111.153(the 4 GitHub Pages IPs)openkline.techAAAAwww.openkline.techrekurt.github.ioCNAMEfileWhat this PR does
Adds a root
CNAMEfile containingopenkline.tech. GitHub Pages requires this file in the publishing source to claim and serve the custom domain; without it the domain is not served by Pages.Important
This file only takes effect if it lands on the branch/source that Pages publishes from (e.g.
masterroot). Merge this into that branch.Still required outside the repo (DNS registrar)
Add the four apex AAAA records so the apex matches GitHub's current health-check expectations:
Then in Settings → Pages, re-enter the custom domain (or click Check again) to force GitHub to re-run the now-stale health check.
Generated by Claude Code