I want to shamelessly plug this:
If you follow this installation, and then do the exact same thing again, but join that server to your new domain, and again, you have 3 servers in your new Samba 4 domain. Note that the other 2 servers NEED to use your Samba container’s IP for DNS.
On either of the other servers you install one of the Nethserver mail server packages, depending on your needs, on the other you install the fileserver role.
I would 1-up this … get a proper NAS, put RAID10 on it, and virtualize all these servers on a HA Proxmox cluster (easy to set up) and store the diskfiles on that.
Depending on network topology, you either let a switch or the FW be the default gateway.
Your first Nethserver uses any public DNS server during it’s install, and uses that to reolve any names that the Samba4 container doesnt know about.
You should NOT!!! use the DNS page on the Nethserver adminpage (unless things changed ?) as the Samba4 container doesnt know about these, and thus your domain doesnt either.
I use above in-company, with a bunch more Nethservers for various web-apps and -sites. This works like a charm.
@danb35 …picture this … 1 Nethserver, 3 webapps. I go to update 1 of them, this FUBAR’s … I now need to restore some stuff … and am forced to reload service httpd … multiple times …
popquiz: what happens to my phone ?
Now picture this: I have 3 Nethservers, 3 webapps, one on each. I update 1 of them … yada yada
My phone rings 1/3 of the times of the previous scenario, and I can blame the (scheduled) update and use the planned downtime window for what it’s for … without 2 other apps being down as well.
Yes I update 3 servers instead of 1 at times, but that time 1 of them gives issues that take longer then expected, you suddenly dont mind any longer 