[DNS] Exposed DNS settings in dash #13149
Open
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
| {{</tab>}} | ||
| {{<tab label="api" no-code="true">}} | ||
|
|
||
| 1. Use the [Edit DNSSEC Status endpoint](/api/operations/dnssec-edit-dnssec-status) to enable DNSSEC and activate multi-signer DNSSEC for your zone. This is done by setting `status` to `active` and `dnssec_multi_signer` to `true`, as in the following example. |
There was a problem hiding this comment.
[cloudflare.UnclearAntecedent] Warning: Instead of 'This is', try starting this sentence with a specific subject and verb.
Deploying cloudflare-docs with
|
| Latest commit: |
fa0e72c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3a0abfc4.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://rebecca-dns-expose-settings.cloudflare-docs-7ou.pages.dev |
RebeccaTamachiro
commented
Mar 1, 2024
| ## Remove account custom nameservers | ||
| 2. Update the registrar of the domain (or domains) that provide the ACNS names. This step depends on whether you are using [Cloudflare Registrar](/registrar/): | ||
|
|
||
| * If you are using Cloudflare Registrar for the domain that provides the ACNS names, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to add glue records to your ACNS and update your nameservers. |
There was a problem hiding this comment.
Is updating nameservers actually necessary at this point (for the domain that provides ACNS names)? Or have we mixed it up with step needed for the zone that will ultimately be assigned an ACNS?
| 2. Make sure `A/AAAA` records with the assigned IPv4 and IPv6 exist at the authoritative DNS of the domain that provides the ACNS names. | ||
|
|
||
| * If your domains use [Cloudflare Registrar](/registrar/), the respective `A` and `AAAA` records are automatically created. |
| {{</example>}} | ||
|
|
||
| 3. Update the registrar of the domain that provides the ACNS names. This step depends on whether you are using [Cloudflare Registrar](/registrar/): |
There was a problem hiding this comment.
Cloudflare Registrar doesn't yet add glue records based on Custom Nameservers setup within Cloudflare.
| {{<tab label="api" no-code="true">}} | ||
|
|
||
| * If you are using [Cloudflare Registrar](/registrar/), use the [Set ACNS Related Zone Metadata endpoint](/api/operations/account-level-custom-nameservers-usage-for-a-zone-set-account-custom-nameserver-related-zone-metadata) to change the `enabled` parameter to `false`. |
There was a problem hiding this comment.
And then contact Cloudflare Support. (like you mentioned above)
|
|
||
| The next step depends on whether you are using [Cloudflare Registrar](/registrar/) for your domain: | ||
|
|
||
| - If you are using Cloudflare Registrar for your domain, no further action is required. Glue records will be added automatically on your behalf. |
pedrosousa
approved these changes
Jun 7, 2024
| While there are default values for DNS settings that Cloudflare applies to all new zones, Enterprise accounts have the option to configure their own DNS zone defaults according to their preference. | ||
|
|
||
| {{<Aside type="warning">}} | ||
| DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted on the respective **DNS > Settings** or **DNS** > **Records** for each zone. |
There was a problem hiding this comment.
Suggested change
| DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted on the respective **DNS > Settings** or **DNS** > **Records** for each zone. | |
| DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted on the respective **DNS** > **Settings** or **DNS** > **Records** for each zone. |
Nit: Are both locations at the zone level or just the second one?
There was a problem hiding this comment.
Both are at the zone level
content/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Pedro Sousa <[email protected]>
This reverts commit 4105816.
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.
PCX-9776
PCX-10635