This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
system:dns [2020-03-13T08:10:35+0000] michael_paoli created |
system:dns [2020-09-07T19:29:25+0000] (current) michael_paoli +Al Whaley |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== DNS ====== | ====== DNS ====== | ||
- | Not that this is //not// a DNS tutorial nor intended to be so. | + | Note that this is //not// a DNS tutorial nor intended to be so. |
It's mostly intended to attempt to reasonably cover documentation of some DNS infrastructure and maintenance thereof, | It's mostly intended to attempt to reasonably cover documentation of some DNS infrastructure and maintenance thereof, | ||
- | and be reasonably accurate at least as of the time of this writing (2020-03-13). | + | and be reasonably accurate at least as of the time of this writing/updating (2020-05-19). |
The BALUG host (balug-sf-lug-v2.balug.org) | The BALUG host (balug-sf-lug-v2.balug.org) | ||
Line 11: | Line 11: | ||
balug.org\\ | balug.org\\ | ||
berkeleylug.com\\ | berkeleylug.com\\ | ||
- | berkeleylug.org\\ | ||
e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa\\ | e.9.1.0.5.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa\\ | ||
sf-lug.com\\ | sf-lug.com\\ | ||
Line 36: | Line 35: | ||
Grant Bowman\\ | Grant Bowman\\ | ||
Rick Moen\\ | Rick Moen\\ | ||
+ | Al Whaley\\ | ||
Note also that there are person(s) who are or may become set up also to edit DNS data for the sub-domain pi.BerkeleyLUG.com (and any subdomains thereof). | Note also that there are person(s) who are or may become set up also to edit DNS data for the sub-domain pi.BerkeleyLUG.com (and any subdomains thereof). | ||
Line 61: | Line 61: | ||
It may also be highly preferable (if not strongly recommended), that rather than edit the zone file, one uses dynamic update to make the DNS changes. | It may also be highly preferable (if not strongly recommended), that rather than edit the zone file, one uses dynamic update to make the DNS changes. | ||
- | Below I give fair bit of example, and more general documentation/explanation:\\ | + | Below I give fair bit of example, and more general documentation/explanation (and with some correction(s)/clarification(s)):\\ |
<file> | <file> | ||
Date: Wed, 11 Mar 2020 01:18:26 -0700 | Date: Wed, 11 Mar 2020 01:18:26 -0700 | ||
Line 176: | Line 176: | ||
Also, one may note, ~root/bin/Named-checkconf | Also, one may note, ~root/bin/Named-checkconf | ||
It's essentially an "enhanced" version of (wrapper around) named-checkconf | It's essentially an "enhanced" version of (wrapper around) named-checkconf | ||
- | and runs relevant checks, and with relevant options/arguments. Not also | + | and runs relevant checks, and with relevant options/arguments. Note also |
to be effective it needs to run as root (to be able to chroot and read | to be effective it needs to run as root (to be able to chroot and read | ||
relevant data, etc.). It's also world readable, so one may view/inspect | relevant data, etc.). It's also world readable, so one may view/inspect |