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

DOCS: Clarify nameserver examples (#1390)

Browse source
This commit is contained in:
Tom Limoncelli 2022-02-02 10:39:58 -05:00 committed by GitHub
parent a3177ebb3d
commit d63ead640d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 26 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
docs/index.md
View file

@ -93,9 +93,6 @@ title: DNSControl
<li>
<a href="{{site.github.url}}/migrating">Migrating</a>: Migrating zones to DNSControl
</li>
<li>
<a href="{{site.github.url}}/cli-variables">CLI variables</a>: Passing variables from CLI to JS
</li>
</ul>
</div>
<div class="col-md-4">
@ -144,6 +141,12 @@ title: DNSControl
<li>
<a href="{{site.github.url}}/code-tricks">Code Tricks</a>: Safely use macros and loops.
</li>
<li>
<a href="{{site.github.url}}/cli-variables">CLI variables</a>: Passing variables from CLI to JS
</li>
<li>
<a href="{{site.github.url}}/nameservers">Nameservers &amp; Delegation</a>: Many examples.
</li>
</ul>
</div>

22
docs/nameservers.md
View file

@ -39,13 +39,17 @@ var DNS_BIND = NewDnsProvider("bind", "BIND");
// ========== Domains:
// "Keep it simple": Use the same provider as a registrar and DNS service.
// ========== Same provider for REG and DNS.
// Keep it simple: Use the same provider as a registrar and DNS service.
// Why? Simplicity.
D("example1.com", REG_NAMECOM,
DnsProvider(DNS_NAMECOM),
A("@", "10.2.3.4")
);
// ========== Different provider for REG and DNS.
// "Separate DNS server": Use one provider as registrar, a different for DNS service.
// Why? Use any registrar but a preferred DNS provider.
// This is the most common situation.
@ -54,7 +58,9 @@ D("example1.com", REG_NAMECOM,
A("@", "10.2.3.4")
);
// Let someone else manage the NS records for a dommain.
// ========== Registrar is elsewhere.
// "DNS only": Let someone else manage the NS records for a dommain.
// Why? Because you don't have access to the registrar, or the registrar is not
// supported by DNSControl. However you do have API access for
// updating the zone's records (most likely at a different provider).
@ -63,6 +69,8 @@ D("example1.com", REG_THIRDPARTY,
A("@", "10.2.3.4")
);
// ========== Zone is elsewhere.
// "Registrar only": Direct the registrar to point to some other DNS provider.
// Why? In this example we're pointing the domain to the nsone.net DNS
// service, which someone else is controlling.
@ -73,6 +81,8 @@ D("example1.com", REG_NAMECOM,
NAMESERVER("dns4.p03.nsone.net."),
);
// ========== Override nameservers.
// "Custom nameservers": Ignore the provider's default nameservers and substitute our own.
// Why? Rarely used unless the DNS provider's API does not support
// querying what the nameservers are, or the API is returning invalid
@ -84,6 +94,8 @@ D("example1.com", REG_NAMECOM,
A("@", "10.2.3.4")
);
// ========== Add nameservers.
// "Add additional nameservers." Use the default nameservers from the registrar but add additional ones.
// Why? Usually only to correct a bug or misconfiguration elsewhere.
D("example1.com", REG_NAMECOM,
@ -92,6 +104,8 @@ D("example1.com", REG_NAMECOM,
A("@", "10.2.3.4")
);
// ========== Shadow nameservers.
// "Shadow DNS servers." Secretly send your DNS records to another server.
// Why? Many possibilities:
/ * You are preparing to move to a different DNS provider and want to test it before you cut over.
@ -104,6 +118,8 @@ D("example1.com", REG_NAMECOM,
A("@", "10.2.3.4")
);
// ========== Backup your zone.
// "Zonefile backups." Make backups of the exact DNS records in zone-file format.
// Why? In addition to the usual configuration, write out a BIND-style
// zonefile perhaps for debugging, historical, or auditing purposes.
@ -114,6 +130,8 @@ D("example1.com", REG_NAMECOM,
A("@", "10.2.3.4")
);
// ========== Dual DNS Providers.
// "Dual DNS Providers": Use two different DNS services:
// Why? Diversity. If one DNS provider goes down, the other will be used.
// Little known fact: Most DNS recursive resolvers monitor which DNS