Update CNAME section for accuracy#62
Open
5731la wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the resolver documentation’s CNAME section to use more precise DNS terminology around CNAME records and their targets.
Changes:
- Rewords the “CNAMEs” section to consistently refer to “CNAME record(s)” instead of “CNAME(s)”.
- Clarifies that resolution restarts for the CNAME target (canonical name).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| CNAME records complicate this process slightly but not fundamentally. A | ||
| CNAME record redirects our query to a new name. This means that once a | ||
| CNAME record is hit, the initial algorithm terminates, and gets restarted | ||
| for the new Canonical Name (CNAME) target. |
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.
I was browsing through some documentation when I came across this free resource with information for the public, and while browsing this I realized that there was a flaw in one of the pages. Once I cleared my eyes, I confirmed that, yes, somebody was WRONG on the INTERNET! Now, as I am unable to disclose which benevolent mega-corporation I am working for where this is relevant, I have had to take this upon myself to anonymously correct this mistake! A fact that is blatantly obvious to the most casual observer!
A CNAME (short for Canonical NAME) record points to the Canonical ("True") Name of that record, therefore the CNAME record is not actually the CNAME but the only type of record that is not its own CNAME.
As a group of people providing free resources to us strangers, you must understand the importance of providing further free labor to us on-demand. As such, I have taken the liberty to update these documents to correct this injustice. I hope this will be a learning experience for all involved.
Context
This is a satirical PR meant as a tongue-in-cheek jab at @ahupowerdns's blog post https://berthub.eu/articles/posts/anonymous-help/. It seemed a little too excessive to go out of my way to make and verify a new github account for this, so I guess I broke the spell slightly.
There is no megacorp who relies on these docs (at least, not one that I'm a part of). I take no offense if this gag-PR is closed. While the information in the changes is, to the best of my knowledge, real and accurate, it's also a pedantic level of correctness that isn't so useful in day-to-day DNS parlance.
Thanks @morrowc for tipping me off to this gag/sending me this way.