- The purpose of this machine is as follows:
- Provide external and internal identity of the "mik-maq.com" network, which will also be identified locally as "BitterGreen" (the wireless name) or "local" (the hostname with .local implied).
- The external identity will be maintained through Dynu.
- Internal "domain" identity will be provided by Pi-Hole with the added benefit of domain ad blocking.
- Does not provide file services managed by a "fileserver" LTK appliance.
- Does not provide a domain certificate, as this is best maintained for and by the webservice open to the external world.
- Does not provide user identity. The plan is to maintain this only on the "fileserver" host, then elsewhere as required per situation.
- Notifications by Gotify are pending, but may be implimented on this host.
- Don't do anything or make changes if not explicitly required by the overall goal.
- I am amiss in not doing a snapshot of the fileserver host before configuring and verifying the rollback process.
- I need to set up automated snapshots vs. recovery as part of this build. I've already done this, but it needs fully worked out within this document.
- I'm seriously considering using the DHCP/DNSMASQ built-in to replace that function within my router. This would not only remove the tedium of manually editing the DNS entries, but the router seems to "hold onto" DNS settings even after I changed it which complicated setting up this host in practice.
- There is a howto on installing Pi-Hole into a Proxmox container. Reference notes follow.
- TKL Core is used consistent with other TKL templates.
- A name of "DNS" dictates what the machine is and does primarily.
- I am using 8 GiB for disk space, 2 Cores, 512 MiB of memory. These values can be changed and updated as required as determined by practical use.
- Logging in at the console, obvious configuations should be entered as obvious (e.g. your email address).
- After the reboot, log back in.
apt update && apt upgrade
would be next.- The "Postfix Configuration" window will come up, presuming no postfix configuation files are present. Select "Local only", then use your FQDN as the domain name.
- This [howto] explains how to set up Pi-hole.
- Pi.hole does an excellent job configuring itself but after the install and configuring your DHCP to provide dns as the primary DNS host, it is wise to reboot all of the machines to be using DNS for that purpose.
- For the purpose of receiving notifications, we need a gotify server. As this host handles various "non-Turnkey Linux" issues, it is the natural place to put the Gotify server.
- Gotify reqires Docker, so follow the [howto] on installing Docker to this instance.
- With Docker installed, follow the directions to install Gotify