StackExchange/dnscontrol
1
1
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2025-01-31 03:53:13 +08:00
Code Issues Projects Releases Packages Wiki Activity

DOCS: Typo Dnscontrol = DNSControl. (#1969)

Browse source 
Co-authored-by: Tom Limoncelli <tlimoncelli@stackoverflow.com>
This commit is contained in:
Jeffrey Cafferata 2023-01-21 23:29:14 +01:00 committed by GitHub
parent d53260703e
commit 9bda481e7e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
documentation/functions/record/SPF_BUILDER.md
View file

@ -224,7 +224,7 @@ else, please do the appropriate equivalent command.
## Caveats
1. Dnscontrol 'gives up' if it sees SPF records it can't understand.
1. DNSControl 'gives up' if it sees SPF records it can't understand.
This includes: syntax errors, features that our spflib doesn't know
about, overly complex SPF settings, and anything else that we we
didn't feel like implementing.
@ -239,7 +239,7 @@ TXT record (not an SPF record, perhaps a TXT record used to verify
domain ownership), the total packet size of all the TXT records
could exceed 512 bytes, and will require EDNS or a TCP request.
3. Dnscontrol does not warn if the number of lookups exceeds 10.
3. DNSControl does not warn if the number of lookups exceeds 10.
We hope to implement this some day.
4. The `redirect=` directive is only partially implemented. We only

2
documentation/get-certs.md
View file

@ -139,7 +139,7 @@ This command is intended to be just a small part of a full certificate automatio
This command is intended to be run as frequently as you desire. One workflow would be to check all certificates into a git repository and run a nightly build that:
1. Clones the cert repo, and the dns config repo (if separate).
2. Decrypt or otherwise obtain the *Let's Encrypt* account private key. Dnscontrol does not need to read any certificate private keys to check or issue certificates.
2. Decrypt or otherwise obtain the *Let's Encrypt* account private key. DNSControl does not need to read any certificate private keys to check or issue certificates.
3. Run `dnscontrol get-certs` with appropriate flags.
4. Encrypt or store any new or updated private keys.
5. Commit and push any changes to the cert repo.

2
documentation/why-the-dot.md
View file

@ -47,7 +47,7 @@ How are they ambiguous?
Yes, we could layer rule upon rule upon rule. Eventually we'd get
all the rules right. However, now a user would have to know all the
rules to be able to use Dnscontrol. The point of the Dnscontrol DSL
rules to be able to use DNSControl. The point of the DNSControl DSL
is to enable the casual user to be able to make DNS updates. By
"casual user" we do not mean someone someone that lives and breathes DNS
like you and I do. In fact, we mean someone that hasn't memorized