system:balug_dns
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
system:balug_dns [2007-05-13T23:40:45+0000] – 198.144.194.236 | system:balug_dns [2020-03-13T07:16:30+0000] (current) – added note about historical ... michael_paoli | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== BALUG DNS ====== | ====== BALUG DNS ====== | ||
+ | |||
+ | **NOTE THAT MOST ALL OF THE DNS INFORMATION ON THIS WIKI PAGE IS HIGHLY OUT-OF-DATE AND MOSTLY ONLY OF HISTORICAL INTEREST. | ||
+ | IT MOSTLY HARKENS BACK TO A TIME WHEN MULTIPLE DISTINCT DNS SERVERS WERE RUNNING ON THE SAME HOST, TO SERVER SEPARATE NEEDS OF | ||
+ | VARIOUS [L]UGs, E.G. BALUG, " | ||
The care and feeding of the **BALUG DNS** server. | The care and feeding of the **BALUG DNS** server. | ||
Line 11: | Line 15: | ||
*it should **not listen on other IPs** (most notably for DNS) | *it should **not listen on other IPs** (most notably for DNS) | ||
*the one exception so far, is it **does listen for control (rndc) connection on a non-default port on 127.0.0.1** - again, **do use the appropriate -balug** commands to avoid accidentally operating on the incorrect DNS server. | *the one exception so far, is it **does listen for control (rndc) connection on a non-default port on 127.0.0.1** - again, **do use the appropriate -balug** commands to avoid accidentally operating on the incorrect DNS server. | ||
- | *The BALUG DNS server runs using user:group balugdns: | + | *The BALUG DNS server runs using user:group balugdns: |
*in general, only superuser (UID 0, a.k.a. " | *in general, only superuser (UID 0, a.k.a. " | ||
- | ***THE PRIMARY PURPOSE FOR THE BALUG DNS SERVER** is for serving DNS zones of interest to BALUG and/or any other such hosting BALUG deems apropriate | + | ***THE PRIMARY PURPOSE FOR THE BALUG DNS SERVER** is for serving DNS zones of interest to BALUG and/or any other such hosting BALUG deems appropriate |
+ | *Note that version control (RCS) has been put in place for at least a few key files, it should be appropriately used to track changes and note the reason(s) //why// change(s) were made. It is also generally advisable to preserve mtimes, e.g.:\\ # ci -d -l -M file | ||
+ | |||
+ | ===== THE STATE OF BALUG.ORG. DNS ===== | ||
+ | **AT LEAST AT THE PRESENT TIME (2007-05-28), | ||
+ | *At least **some Internet DNS //has// been delegated to this DNS server** (but not yet balug.org.) | ||
+ | *This is subject to change - most current information can probably be found by: | ||
+ | *having a look at file:/ | ||
+ | *or of course, making the appropriate Internet DNS queries | ||
+ | *as of 2007-05-26 this host //should// have complete balug.org. zone data (can't do a zone transfer, but as of 2007-05-26 at least Michael Paoli and Jim Stockford should have the access to review what should be all the data that's in the delegated balug.org. DNS), hence the zone data on this host //should// be complete (with some additional bits of data such as SOA and TTLs determined via responses to DNS queries); it is // | ||
+ | *the various configuration and zone files contain much more relevant detail, including what's noted in the comments. |
system/balug_dns.1179099645.txt.bz2 · Last modified: 2007-05-13T23:40:45+0000 by 198.144.194.236