Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
opennic:setup:webminbind:debian9u0webmin1u9base [2020-03-18T18:47:53Z] – [Zone Defaults] fouroh-llc | opennic:setup:webminbind:debian9u0webmin1u9base [2020-03-26T19:11:38Z] – fouroh-llc | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Debian 9 with Webmin 1.9xx Fresh Install ===== | + | Configuration, |
- | Again, please make sure you install from within | + | http:// |
+ | Yyet from the shell it seems to work fine. | ||
+ | {{: | ||
+ | |||
+ | ===== Fresh Install ===== | ||
+ | This page includes a very brief overview of Webmin | ||
{{: | {{: | ||
+ | In the upper left corner the icon that looks like a gear is the Module Config. In the upper right corner the icon looks like a " | ||
- | In the upper left corner the icon that looks like a gear is the Module Config. In the upper right corner the icon looks like a play button starts the service. Before we start, however, lets look at the //home// of bind9. | ||
{{: | {{: | ||
+ | The location and the list of files might be different on a different distribution (Red-Hat, Slackware, or from Enterprises like Oracle). | ||
- | Those which are going to be our concern are discussed below. The db.root file is a special case, where the change from the InterNIC TLDs to the OpenNIC TLDS actually happen. For the record, the content of the db.root file, at the time of writing this, is listed [[db_root_file-content|here]]. On OpenNIC Tier-1 servers the file should read something like below: | + | ==== Backup and Archive==== |
- | < | + | The difference between backup and archive is the location where they are stored - one is on-line, but going to be lost when the host is lost. The other is off-line, but remains available. These are your choices for backup: |
- | ; This file holds the information ... | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS2.OPENNIC.GLUE. | + | |
- | NS2.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS4.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS5.OPENNIC.GLUE. | + | |
- | NS5.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS6.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS8.OPENNIC.GLUE. | + | |
- | NS8.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . 3600000 | + | |
- | NS9.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . | + | |
- | NS10.OPENNIC.GLUE. | + | |
- | NS10.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . | + | |
- | NS11.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . | + | |
- | NS12.OPENNIC.GLUE. | + | |
- | ; | + | |
- | . | + | |
- | NS13.OPENNIC.GLUE. | + | |
- | NS13.OPENNIC.GLUE. | + | |
- | </ | + | |
- | ==== named.conf.default-zones ==== | + | Use the listed above to plan and test your capacity to recover from errors, attacks or even from ransomware. These are very basic, simple measures to keep your service stacks functional. |
- | The content of this file not supposed | + | |
- | < | + | |
- | // prime the server with knowledge of the root servers | + | |
- | zone "." { | + | |
- | type hint; | + | |
- | file "/ | + | |
- | }; | + | |
- | // be authoritative for the localhost forward | + | {{: |
- | // broadcast zones as per RFC 1912 | + | Linode backups |
- | zone " | + | {{: |
- | type master; | + | Webmin allows scheduling and creating compressed archives of targeted part of your instance. |
- | file "/ | + | |
- | }; | + | |
- | zone " | + | {{: |
- | type master; | + | Recover from off-line backup in case of sustained attack going back for weeks or months. |
- | file "/ | + | |
- | }; | + | |
- | zone "0.in-addr.arpa" { | + | ==== User Management ==== |
- | type master; | + | User management from the shell is expanded by Webmin several ways. The most advanced is Usermin via LDAP, which is not really necessary on single instances. However, using the Webmin Users and Groups modules is necessary to allow login via Webmin |
- | file "/ | + | |
- | }; | + | |
- | zone " | + | {{: |
- | type master; | + | Webmin Users and Groups control access to Modules - but the UNIX user must also exist. |
- | file "/ | + | |
- | }; | + | |
- | </ | + | |
- | As you see, the db.root file is included here, and the rest of the file content has to do with proper networking setup on the host. Later while adding / removing name servers the two most common directives added by Webmin going to be " | + | ==== Module Management |
- | + | These should be the IP4 addresses of the OpenNIC Tier-2s. Normally | |
- | ==== named.conf | + | |
- | This file should | + | |
- | < | + | |
- | // This is the primary configuration file for the BIND DNS server named. | + | |
- | // | + | |
- | // Please read / | + | |
- | // structure of BIND configuration files in Debian, *BEFORE* | + | |
- | // this configuration file. | + | |
- | // | + | |
- | // If you are just adding zones, please do that in / | + | |
- | + | ||
- | include "/ | + | |
- | include "/ | + | |
- | include "/ | + | |
- | </ | + | |
- | + | ||
- | The file // | + | |
- | + | ||
- | The file //named.conf.local// going to hold our master and slave zones (called domains). Before we start up lets archive /etc/bind to save the original configuration. | + | |
- | + | ||
- | ==== Backup and Archive==== | + | |
- | The difference between backup and archive is the location where they are stored | + | |
- | {{: | + | |
- | DNS is all about redundancy, so configuring email notification about backup | + | {{: |
+ | The DNS administrator has full access | ||
- | ==== Start BIND | + | ==== Network Security |
- | Once you create and RESTORE | + | Debian does not assume anything about the purpose of the system, it does not install or configure additional software, and it does not start services by default. // |
- | === Setup RNDC === | + | {{: |
- | This is going to fail if, for any reason, the loop-back interface (127.0.0.1) | + | If you start iptables with a wrong configuration |
- | === Zone Defaults | + | ==== Webmin Modules ==== |
- | This configures | + | Some modules in Webmin are matured and well-rounded - the BIND module, |
- | {{: | + | |
- | What is not shown depends on your installation. The screenshot shows the current host name - which you should ignore. Instead enter the FQDN of your name server, NSx.YOURDOMAIN.TLD or NSx.SUBDOMAIN.YOURDOMAIN.TLD. Consequently the //Default email address// should correspond the same way (admin@yourdomain.tld), | + | {{: |
+ | Webmin has good support for FirewallD | ||
- | The DNSSEC settings are set to the largest-size keys as all other are very much discounted these days. You may set it higher, but only if OpenNIC recommends it. | + | ==== Logging ==== |
+ | Webmin provides access | ||
- | I leave the transfer and query settings to be managed by each zone and leave them here blank / default. | + | {{: |
+ | Security starts with these logs, as nearly all attacks | ||
+ | ==== Conclusion ==== | ||
+ | You may write your own scripts and use a tool such as Ansible to do more, better than what Webmin does. However, Webmin makes your instances much friendlier inside an environment without Information Technology professionals expert with GNU/Linux. On a factory floor, for example, Webmin is able to serve engineers, managers, production workers with much less training than full-featured but more complex tools. | ||