I think this was my error by selecting DNS for a VS (accepting the default - why is it a default? on creation) before I realised it was not required and deselecting it. (All my VS DNS are managed externally on the provider’s NS).
but doesn’t confirm it is not wanted or suggest how to get rid of it. Even as it is not running. I thought there was a way of removing it somewhere (which I must have done on the production server) where running the recheck configuration does not say it is installed.
Thought that would kill / remove it wouldn’t you?
but doing so and rebooting still seems to leave the system wanting it and now recheck config complains. I doubt if it was done that way on the production box - just that I never ticked (or rather unticked the “setup DNS zone” on creating the VS)
However I may have found it in deselecting System Settings -> Features & Plugins -> DNS Domain
I’m amazed I found that on the production server.
That’s not an option, AFAIK, and autoremove is a terrifyingly risky proposition if not used with care, and if you’ve ever removed any package that the Virtualmin metapackage depends on (because then all of the Virtualmin stack becomes eligible for autoremove), without manually marking them with install. We’ve seen folks blow away their whole system using autoremove, after removing packages that are Virtualmin dependencies. It can be extremely destructive if you don’t read what packages are being removed before continuing.
I think I have to emphasise and clarify that this was the solution. Not --auto-remove.
It is performed wholly within Virtualmin (and therefore presumably well thought through as a process and is reversible should you ever require DNS management in the future)
Virtualin is complex and covers many things some of which can be seen to be obscure and deep inside menus but as I noted at the top of this topic I had lost my notes on where I had found it and what it actually did.