Nameserver(s) are not Responsive

The system diagnostic is showing a problem of Nameserver(s) are not responsive, there appears to be an issue with the python script? Here is the output:

Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/init.py”, line 250, in execute
ret = execute(umc_module, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/univention/management/console/modules/diagnostic/plugins/11_nameserver.py”, line 55, in run
MODULE.error(‘%s%s’, description, len(failed), ‘\n’.join(failed))
File “/usr/lib/python3/dist-packages/univention/logging.py”, line 485, in error
_self._log(_self.__log.error, _message, *_args, **_kwargs)
File “/usr/lib/python3/dist-packages/univention/logging.py”, line 504, in _log
return _func(
^^^^^^
File “/usr/lib/python3.11/logging/init.py”, line 1518, in error
self._log(ERROR, msg, args, **kwargs)
File “/usr/lib/python3.11/logging/init.py”, line 1634, in _log
self.handle(record)
File “/usr/lib/python3.11/logging/init.py”, line 1644, in handle
self.callHandlers(record)
File “/usr/lib/python3.11/logging/init.py”, line 1706, in callHandlers
hdlr.handle(record)
File “/usr/lib/python3.11/logging/init.py”, line 978, in handle
self.emit(record)
File “/usr/lib/python3/dist-packages/univention/logging.py”, line 616, in emit
msg = self.format(record)
^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/logging/init.py”, line 953, in format
return fmt.format(record)
^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/univention/logging.py”, line 359, in format
record.message = record.getMessage().replace(‘\t|’, ‘\t\|’)
^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/logging/init.py”, line 377, in getMessage
msg = msg % self.args
^~~~~~~
TypeError: not all arguments converted during string formatting
“Network settings” module

I get the error on the primary, backup and member servers. At times the error disappears on all but the primary server?

Resolved - I had a policy applied to the primary server for the DNS/forwarders. #2 & #3 were not reachable. I removed the policy and unset the values on all three systems, so dns/forwarder1 was only set via the UMC. System Diagnostic has no errors.