Differences

This shows you the differences between two versions of the page.

--- opennic:setup:webminbind:debian9u0webmin1u9base [2020-03-18T17:35:39Z] – [named.conf] fouroh-llc
+++ opennic:setup:webminbind:debian9u0webmin1u9base [2020-03-27T11:44:12Z] (current) – fouroh-llc
@@ Line 1: / Line 1: @@
-===== Debian 9 with Webmin 1.9xx Fresh Install =====
+===== Fresh Install =====
-Again, please make sure you install from within Webmin (Unused Modules) then Refresh Modules to move the BIND link under Servers. This is the default screen.
+This page includes a very brief overview of Webmin module screens, before turning the instance into a Tier-2 service stack. The page is going to grow and expand as feedback comes in for better, more detailed explanations. If you are already familiar with Webmin, or you do not wish to use it you may skip this page entirely.
 {{:opennic:setup:webminbind:base-001.png|The newly installed Webmin BIND module}}
+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. When you configure RDC a "Refresh" button is added. Do not yet start it, but lets look at its home directory.
-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.
 {{:opennic:setup:webminbind:base-002.png|The location and content of BIND's home}}
+The location and the list of files might be different on a different distribution (Red-Hat, Slackware, or from Enterprises like Oracle).
+==== 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:
+  * A manual snapshot by Linode, which you should use for milestones such as before distribution upgrades.
+  * Three automated backups by Linode, which you should use to recover from errors or attacks.
+  * A compressed archive by Webmin, which you should use to save parts of the filesystem
+  * A download / upload utility by Webmin, to keep off-line copies of your archives.
+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.
+{{:opennic:setup:webminbind:base-010.png|Webmin Filesystem Backup with scheduling}}
+Linode backups and restores never fail, but they replace your ENTIRE instance.
+{{:opennic:setup:webminbind:base-003.png|Webmin Filesystem Backup with scheduling}}
+Webmin allows scheduling and creating compressed archives of targeted part of your instance.
+{{:opennic:setup:webminbind:base-004.png|Save and restore copies of your on-line backup}}
+Recover from off-line backup in case of sustained attack going back for weeks or months.
+==== User Management ====
+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 - otherwise the user is limited to ssh login only. Also - on production servers Webmin shall not be installed to reduce the number of software exploits.
+{{:opennic:setup:webminbind:base-005.png|Extended functionally for UNIX Users and Groups by Webmin}}
+Webmin Users and Groups control access to Modules - but the UNIX user must also exist.
+==== Module Management ====
+These should be the IP4 addresses of the OpenNIC Tier-2s. Normally you use Google's 8.8.8.8 here, but if you enter only that this name-server is NOT going to function. Also note - this is different from the settings of your VPS network, which SHOULD use Google's.
-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:
+{{:opennic:setup:webminbind:base-006.png|The DNS Administrator login}}
-<code>
+The DNS administrator has full access to the DNS module and a few others like backup/restore and download/upload.
-;       This file holds the information ...
-;
-.                      3600000      NS    NS2.OPENNIC.GLUE.
-NS2.OPENNIC.GLUE.      3600000      A     161.97.219.84
-NS2.OPENNIC.GLUE.      3600000      AAAA  2001:470:4212:10:0:100:53:10
-;
-.                      3600000      NS    NS4.OPENNIC.GLUE.
-NS4.OPENNIC.GLUE.      3600000      A     163.172.168.171
-;
-.                      3600000      NS    NS5.OPENNIC.GLUE.
-NS5.OPENNIC.GLUE.      3600000      A     94.103.153.176
-NS5.OPENNIC.GLUE.      3600000      AAAA  2a02:990:219:1:ba:1337:cafe:3
-;
-.                      3600000      NS    NS6.OPENNIC.GLUE.
-NS6.OPENNIC.GLUE.      3600000      A     207.192.71.13
-;
-.                      3600000      NS    NS8.OPENNIC.GLUE.
-NS8.OPENNIC.GLUE.      3600000      A     178.63.116.152
-NS8.OPENNIC.GLUE.      3600000      AAAA  2a01:4f8:141:4281::999
-;
-.                      3600000      NS    NS9.OPENNIC.GLUE.
-NS9.OPENNIC.GLUE.      3600000      A     51.77.227.84
-;
-.                       3600000      NS    NS10.OPENNIC.GLUE.
-NS10.OPENNIC.GLUE.      3600000      A     188.226.146.136
-NS10.OPENNIC.GLUE.      3600000      AAAA  2001:470:1f04:ebf::2
-;
-.                       3600000      NS    NS11.OPENNIC.GLUE.
-NS11.OPENNIC.GLUE.      3600000      A     51.75.173.177
-;
-.                       3600000      NS    NS12.OPENNIC.GLUE.
-NS12.OPENNIC.GLUE.      3600000      A     79.124.7.81
-;
-.                       3600000      NS    NS13.OPENNIC.GLUE.
-NS13.OPENNIC.GLUE.      3600000      A     144.76.103.143
-NS13.OPENNIC.GLUE.      3600000      AAAA  2a01:4f8:192:43a5::2
-</code>
-==== named.conf.default-zones ====
+==== Network Security ====
-The content of this file not supposed to be changed by hand, and a new BIND instance has it as:
+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. //iptables// is an exception to this, it is installed by default. However, it is not configured and it is not started. If you have installed a firewall software such as FirewallD - iptables is going to be started and managed by that software.
-<code>
-// prime the server with knowledge of the root servers
-zone "." {
-	type hint;
-	file "/etc/bind/db.root";
-};
-// be authoritative for the localhost forward and reverse zones, and for
+{{:opennic:setup:webminbind:base-007.png|Firewall is not configured by default}}
-// broadcast zones as per RFC 1912
+If you start iptables with a wrong configuration you might lose access to your instance!
-zone "localhost" {
+==== Webmin Modules ====
-	type master;
+Some modules in Webmin are matured and well-rounded - the BIND module, for example. Some are obsolete, no longer maintained, and these days they are only included for backwards compatibility - such as the Jabber IM Server. Some are mature and install from within Webmin, some needs to be installed from the shell and tell Webmin to look for them "Refresh Modules".
-	file "/etc/bind/db.local";
-};
-zone "127.in-addr.arpa" {
+{{:opennic:setup:webminbind:base-008.png|Module installation}}
-	type master;
+Webmin has good support for FirewallD - but it must be installed from the shell.
-	file "/etc/bind/db.127";
-};
-zone "0.in-addr.arpa" {
+==== Logging ====
-	type master;
+Webmin provides access to several logging facilities, with management for logging added for BIND and for Webmin.
-	file "/etc/bind/db.0";
-};
-zone "255.in-addr.arpa" {
+{{:opennic:setup:webminbind:base-009.png|The standard UNIX logs }}
-	type master;
+Security starts with these logs, as nearly all attacks leave some clues in these logs.
-	file "/etc/bind/db.255";
-};
-</code>
-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 "also-notify" and "allow-transfer".
+==== 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.
-==== named.conf ====
-This file should not be edited by hand, and it is not edited by Webmin:
-<code>
-// This is the primary configuration file for the BIND DNS server named.
-//
-// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
-// structure of BIND configuration files in Debian, *BEFORE* you customize
-// this configuration file.
-//
-// If you are just adding zones, please do that in /etc/bind/named.conf.local
-include "/etc/bind/named.conf.options";
-include "/etc/bind/named.conf.local";
-include "/etc/bind/named.conf.default-zones";
-</code>
-The file //named.conf.default-zones// includes //db.root//, and the file //named.conf.options// holds the BIND daemon's operating parameters.
-The file //named.conf.local// going to hold our primary and slave zones (called domains). Before we start up lets archive /etc/bind to save the original configuration.