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-18T17:35:39Z] – [named.conf] fouroh-llc | opennic:setup:webminbind:debian9u0webmin1u9base [2020-03-26T19:10:40Z] – fouroh-llc | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Debian 9 with Webmin 1.9xx Fresh Install ===== | + | Configuration, |
- | Again, please make sure you install from within | + | {{: |
+ | |||
+ | ===== 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). | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | {{: | ||
+ | Linode backups and restores never fail, but they replace your ENTIRE instance. | ||
+ | |||
+ | {{: | ||
+ | Webmin allows scheduling and creating compressed archives of targeted part of your instance. | ||
+ | |||
+ | {{: | ||
+ | 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. | ||
+ | |||
+ | {{: | ||
+ | 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' | ||
- | 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}} |
- | < | + | The DNS administrator has full access to the DNS module and a few others like 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 | + | ==== Network Security |
- | The content | + | Debian does not assume anything about the purpose |
- | < | + | |
- | // 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 | + | {{: |
- | // 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 "/ | + | |
- | }; | + | |
- | zone " | + | {{: |
- | type master; | + | Webmin has good support for FirewallD - but it must be installed from the shell. |
- | file "/ | + | |
- | }; | + | |
- | zone " | + | ==== Logging ==== |
- | type master; | + | Webmin provides access to several logging facilities, with management for logging added for BIND and for Webmin. |
- | file "/ | + | |
- | }; | + | |
- | zone " | + | {{: |
- | type master; | + | Security starts with these logs, as nearly all attacks leave some clues in these logs. |
- | 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 | + | ==== Conclusion ==== |
+ | You may write your own scripts | ||
- | ==== named.conf ==== | ||
- | This file should not be edited by hand, and it is not edited by Webmin: | ||
- | < | ||
- | // This is the primary configuration file for the BIND DNS server named. | ||
- | // | ||
- | // Please read / | ||
- | // structure of BIND configuration files in Debian, *BEFORE* you customize | ||
- | // this configuration file. | ||
- | // | ||
- | // If you are just adding zones, please do that in / | ||
- | include "/ | ||
- | include "/ | ||
- | include "/ | ||
- | </ | ||
- | The file // | ||
- | The file // |