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

3
docs/nameservers.md
View File

@@ -47,7 +47,7 @@ NS records for the base domain should not be specified manually, as that will re
{% include alert.html text="Note: Not all providers allow full control over the NS records of your zone. It is not recommended to use these providers in complicated scenarios such as hosting across multiple providers. See individual provider docs for more info." %}
DnsControl will also register the authoritative nameserver list with the registrar, so that all nameserver are used in the tld registry.
DNSControl will also register the authoritative nameserver list with the registrar, so that all nameserver are used in the TLD registry.
## 3. Backup providers
@@ -57,4 +57,3 @@ Its nameservers will not be added to the authoritative set. While this may seem
1. Backup nameservers will still be updated with the NS records from the authoritative nameserver list. This means the records will still need to be updated to correctly "activate" the provider.
2. Costs generally scale with utilization, so there is often no real savings associated with an active-passive setup vs an active-active one anyway.