New problems with that in DNS servers in Hostname and DNS Client -> DNS Client Options. Cant run Virtualmin -> System Settings -> Re-Check Configuration

I know something changed recently, but I don't know exactly when because the things that are going wrong aren't things I check on or use daily. I gave a whirl at posting on the forum, but so far it's no help. (

I'm a rare Virtualmin customer who works behind a Dynamic IP and uses the Community version of Virtualmin despite paying annually for the next better version.

Somehow, the way I would go into Webmin -> Networking -> Network Configuration -> Hostname and DNS Client -> DNS Client Options -> DNS servers: to add back in the has changed. I believe it to be a Virtualmin problem. No attempts to put the value in their stick. All attempts to run Virtualmin -> System Settings -> Re-Check Configuration fail.

Because of wandering around today trying to find solutions I ran a command and was surprised to see the number I couldn't seem to put in was instantiated on my system live:

systemd-resolve --status
         DNS Servers:

So it appears I have a Shroedingers-Cat; it's there and it ain't there.

Another very related symptom I'm having is my Collabora Office part of my Nextcloud server stopped working in a new way. It seems to be related to the inability to proxy pass off of This has never happened to me before with Collabora and I've been running it for many years now. The URL for the office part works and its cert is still valid.

I'm not sure what to do next to help solve this problem.

Virtualmin version: 
Webmin version: 


If you want, you can just turn off the check in Virtualmin for having in your DNS config - this can be done on the Virtualmin Configuration page, under Advanced options.

WNYmathGuy's picture
Submitted by WNYmathGuy on Sun, 12/06/2020 - 13:04 Pro Licensee

Okay, I disabled the check for resolve.conf because I assumed that's what you meant. The Virtualmin -> System Settings -> Re-Check Configuration worked after that, but I still don't have my Collabora working. Could be a lot of reasons for that though. I looked into a bunch of posts about this and so far none of the solutions to the same error message fit my Collabora problem.