Update dns-record-types.mdx #19417
Merged
Update dns-record-types.mdx #19417
Conversation
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
SOA records require an Account Entitlement for ENT customers, not enabled by default: Authoritative DNS - Custom SOA Record Allowed, so customers may need to reach out to support or their account teams to enable it
Contributor
|
Not merging yet, while I check the expected behavior with the team. |
RebeccaTamachiro
approved these changes
Feb 3, 2025
workers-devprod
added
the
contribution
|
Congratulations @vianaedson, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm6pd18ac136240ci998p71y1d This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
SOA records require an Account Entitlement for ENT customers, not enabled by default: Authoritative DNS - Custom SOA Record Allowed, so customers may need to reach out to support or their account teams to enable it
Summary
Customer in ticket 01217536 tried to edit RNAME in SOA and got errors. Troubleshooting it led to find that this entitlement needed to be enabled, but neither the customer or the owner TSE knew about it
Screenshots (optional)
Documentation checklist