Univention Bugzilla – Bug 37273
Extend the domain controller not found message
Last modified: 2019-01-03 07:17:50 CET
Currently, I get the following message if I try to install a slave and a DC wasn't found: No domain controller was found at the address of the name server. It is recommended to verify that the network settings are correct. It is unclear what correct means. We should add a hint that in most scenarios the domain controller master should be used as name server. Or at least one of the existing UCS DCs.
*** This bug has been marked as a duplicate of bug 37263 ***
(In reply to Alexander Kläser from comment #1) > > *** This bug has been marked as a duplicate of bug 37263 *** Not really a duplicate, I was too fast.
(In reply to Stefan Gohmann from comment #0) > Currently, I get the following message if I try to install a slave and a DC > wasn't found: > > No domain controller was found at the address of the name server. It is > recommended to verify that the network settings are correct. > > It is unclear what correct means. We should add a hint that in most > scenarios the domain controller master should be used as name server. Or at > least one of the existing UCS DCs. Furthermore we should add a hint which DNS records need to be found, for example Bug #37501 for the reverse pointer. To make it clear, in this bug we should only adjust the messages.
If I see it correctly, this doesn't happen very often. Reset target milestone.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.