Patch 1 #30
Closed
Patch 1 #30
Conversation
This file contains 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
The DNS instructions in RFC1034 (section 3.6.2) state that, if a CNAME record is present at a node, no other data should be present. This ensures the data for a canonical name and its aliases cannot be different. Because an apex domain requires NS records and usually other records like MX to make it work, setting a CNAME at the apex would break the "no other data should be present" rule. As a CNAME record is not allowed to coexist with any other data, having the apex domain as a CNAME can cause issues, for example with MX (mail). The RFC standard is to use type A for apex (ex: example.com) and CNAME for subdomains (ex: www.example.com)
…E record is present at a node, no other data should be present. This ensures the data for a canonical name and its aliases cannot be different. Because an apex domain requires NS records and usually other records like MX to make it work, setting a CNAME at the apex would break the "no other data should be present" rule. As a CNAME record is not allowed to coexist with any other data, having the apex domain as a CNAME can cause issues, for example with MX (mail). The RFC standard is to use type A for apex (ex: example.com) and CNAME for subdomains (ex: www.example.com)
…E record is present at a node, no other data should be present. This ensures the data for a canonical name and its aliases cannot be different. Because an apex domain requires NS records and usually other records like MX to make it work, setting a CNAME at the apex would break the "no other data should be present" rule. As a CNAME record is not allowed to coexist with any other data, having the apex domain as a CNAME can cause issues, for example with MX (mail). The RFC standard is to use type A for apex (ex: example.com) and CNAME for subdomains (ex: www.example.com)
…E record is present at a node, no other data should be present. This ensures the data for a canonical name and its aliases cannot be different. Because an apex domain requires NS records and usually other records like MX to make it work, setting a CNAME at the apex would break the "no other data should be present" rule. As a CNAME record is not allowed to coexist with any other data, having the apex domain as a CNAME can cause issues, for example with MX (mail). The RFC standard is to use type A for apex (ex: example.com) and CNAME for subdomains (ex: www.example.com)
hguthrie
added
internal
|
Closing, these changes have been made |
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.
Purpose of this pull request
The DNS instructions in RFC1034 state that, if a CNAME record is present at a node, no other data should be present. This ensures the data for a canonical name and its aliases cannot be different. Because an apex domain requires NS records and usually other records like MX to make it work, setting a CNAME at the apex would break the "no other data should be present" rule.
The RFC standard is to use type A for apex (ex: example.com) and CNAME for subdomains (ex: www.example.com)
Affected pages
help/cloud-guide/launch/checklist.md