theory-masters.md

@@ -44,6 +44,10 @@ Docker is used to host the database and frontend elements - it is here that the
 
 The actual frontend configuration consists of three individual containers, set up via docker-compose from locally-built Dockerfiles. There is a cronjob running once a minute, attempting to pull any updates to the frontend git repo, and if there is one, updating the running containers using docker-compose.
 
+## Additional Functions - DNS
+
+An internal DNS server is provided as part of the master services, to allow for a more intuitive control scheme. This service is controlled via Pacemaker, and is statically built, defining a new internal Top Leve. Domain (tld) of .broc for all known IPs inside the machine config.
+
 ### Secondary master installation
 
 Once a new secondary master is entered into the database and the dhcpd config updated, when booted onto the network this machine will automatically get an SSH key from the current master and then SSH back into it as user master-builder, opening a socket file for itself there. By doing this, it exposes a shell on this new machine, with the initramfs as its base filesystem in memory. There is a second script that can then be run, which will install this second master via the socket file, allowing it to use that key to log in as root on the current master and clone the entire filesystem.