Skip to content

Fix wording in rfc2136 documentation on rate limits #1824

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix wording in rfc2136 documentation on rate limits #1824

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
6 changes: 3 additions & 3 deletions content/docs/configuration/acme/dns01/rfc2136.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,11 +161,11 @@ Note how the `tsig-secret` and `tsig-secret-key` match the configuration in the

## Rate Limits

The `rfc2136` provider waits until *all* nameservers to in your domain's SOA RR
The `rfc2136` provider waits until *all* nameservers authoritative for your domain
respond with the same result before it contacts Let's Encrypt to complete the
challenge process. This is because the challenge server contacts a
non-authoritative DNS server that does a recursive query (a query for records it
does not maintain locally). If the servers in the SOA do not contain the correct
does not maintain locally). If not all the authoritative servers contain the correct
values, it's likely that the non-authoritative server will have bad information
as well, causing the request to go against rate limits and eventually locking
the process out.
Expand Down Expand Up @@ -204,4 +204,4 @@ requested, the provider will begin processing the request.
- Compared to the other providers that often use REST APIs to modify DNS RRs,
this provider can take a little longer. You can `watch kubectl certificate
yourcert` to get a display of what's going on. It's not uncommon for the process
to take five minutes in total.
to take five minutes in total.