Skip to content

Added information about TSIG usage on linked peers #15876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Added information about TSIG usage on linked peers #15876

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion content/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,14 @@ To link a primary zone to a peer using the API, send a [POST](/api/operations/se
{{</tab>}}
{{</tabs>}}

{{

}}
For security reasons TSIGs are considered a zone level configuration, this means that if one of the linked peer configured on a zone has a TSIG then all the linked peers on that zone are expected to make zone transfer requests using the same TSIG
{{

}}

## Step 4 - Create an ACL

When you create an Access Control List (ACL), that list contains the source IP addresses that are allowed to send zone transfer requests. If you do not configure an ACL, your zone transfers will fail from IP addresses other than the one specified in the peer DNS server linked to your primary zone on Cloudflare.
Expand Down Expand Up @@ -177,4 +185,4 @@ To enable outgoing zone transfers using the API, send a [POST](/api/operations/s

## Step 8 - Add secondary nameservers to registrar

At your registrar, add the nameservers of your secondary DNS provider.
At your registrar, add the nameservers of your secondary DNS provider.