When I was finalising the Webmin/Virtualmin install process it asked if I wanted local DNS or not, and I chose no. I see there’s a directory /etc/bind and process for /usr/sbin/named -f -u bind, but not sure how my choice during install effects the necessary configuration, or if I need to somehow backtrack and tell it to use local DNS explicitly.
Even if there’s not yet external DNS pointing the domain in question to the server? I would have thought it’s necessary to use the same FQDN as will be served, which means having to switch the A record at least beforehand…
For SPF I should just need to add the new/additional ip: to the record for each domain. For DKIM, presumably if Virtualmin sets up a subdomain (eg. mail._domainkey...) that doesn’t conflict with what I’m already using, or I issue the commands manually via the cli, it shouldn’t interfere with having MX still pointed to the original server. I’m okay with that setup process. Just need to confirm how Virtualmin would handle it so I can make sure I correctly manage the sequence of steps to migrate when the time comes. Getting TLS certs out of the way is step one in any case, even if initially I just manually copy the existing one’s from /etc/letsencrypt into place from the old server (and temporarily point the apache2 config at them before Virtualmin does it’s thing). I just don’t want to do something manually that will bite me later if/when I use Virtualmin (eg. should I setup domains with Virtualmin first, and then do the manual stuff, or the other way around).
PS. This probably goes without saying, but I sincerely appreciate your patience with all my questions.