mirror/stackexchange-dnscontrol
1
0
Fork 0
mirror of https://github.com/StackExchange/dnscontrol.git synced 2024-05-11 05:55:12 +00:00
Code Issues Releases Activity

DOC: Apply brand-preferred case (#429)

Browse Source 
* Apply brand-preferred case

* Apply case to own branding as well
This commit is contained in:
Nikolay Kolev
2019-05-23 06:29:21 -07:00
committed by Tom Limoncelli
parent 608dd7af56
commit b3e35b56a2
15 changed files with 32 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/_functions/domain/CF_TEMP_REDIRECT.md
View File

@@ -5,7 +5,7 @@ parameters:
- modifiers...
---
`CF_REDIRECT` uses CloudFlare-specific features ("page rules") to
`CF_REDIRECT` uses Cloudflare-specific features ("page rules") to
generate an HTTP 301 redirect.
WARNING: If the domain has other pagerules in place, they may be

2
docs/_functions/domain/NO_PURGE.md
View File

@@ -7,7 +7,7 @@ Records will be added and updated, but not removed.
NO_PURGE is generally used in very specific situations:
* A domain is managed by some other system and DNSControl is only used to insert a few specific records and/or keep them updated. For example a DNS Zone that is managed by ActiveDirectory, but DNSControl is used to update a few, specific, DNS records. In this case we want to specify the DNS records we are concerned with but not delete all the other records. This is a risky use of NO_PURGE since, if NO_PURGE was removed (or buggy) there is a chance you could delete all the other records in the zone, which could be a disaster. That said, domains with some records updated using Dynamic DNS have no other choice.
* A domain is managed by some other system and DNSControl is only used to insert a few specific records and/or keep them updated. For example a DNS Zone that is managed by Active Directory, but DNSControl is used to update a few, specific, DNS records. In this case we want to specify the DNS records we are concerned with but not delete all the other records. This is a risky use of NO_PURGE since, if NO_PURGE was removed (or buggy) there is a chance you could delete all the other records in the zone, which could be a disaster. That said, domains with some records updated using Dynamic DNS have no other choice.
* To work-around a pseudo record type that is not supported by DNSControl. For example some providers have a fake DNS record type called "URL" which creates a redirect. DNSControl normally deletes these records because it doesn't understand them. NO_PURGE will leave those records alone.
In this example DNSControl will insert "foo.example.com" into the