To me, this looks the same bug present here: 43745 – Master join as AD member fails due to old _domaincontroller_master._tcp record
described here:
Any thoughts if this is the case, or how I can resolve this and use Univention again? Thanks for your help
root@ucs-bdc:~# samba-tool domain info 192.168.2.79
ERROR: Invalid IP address ‘192.168.2.79’!
root@ucs-bdc:~# samba-tool domain info 192.168.2.91
ERROR: Invalid IP address ‘192.168.2.91’!
root@ucs-bdc:~# samba-tool domain info 127.0.0.1
ERROR: Invalid IP address ‘127.0.0.1’!
root@ucs-bdc:~#
I may be getting closer!
root@ucs-bdc:~# univention-check-join-status
Warning: ‘nextcloud’ is not configured.
Warning: ‘univention-samba4’ is not configured.
Warning: ‘univention-samba4-dns’ is not configured.
Warning: ‘univention-samba4-saml-kerberos’ is not configured.
Error: Not all install files configured: 4 missing
and:
Running 50nextcloud.inst failed (exitcode: 1)
Running 50wekan.inst skipped (already exec uted)
Running 50wordpress.inst skipped (already exec uted)
Running 81univention-ad-connector.inst skipped (already exec uted)
Running 81univention-nfs-server.inst skipped (already exec uted)
Running 90univention-bind-post.inst skipped (already exec uted)
Running 91univention-saml.inst skipped (already exec uted)
Running 92univention-management-console-web-server.inst skipped (already exec uted)
Running 96univention-samba4.inst failed (exitcode: 1)
Running 98univention-pkgdb-tools.inst skipped (already exec uted)
Running 98univention-samba4-dns.inst failed (exitcode: 1)
Running 98univention-samba4-saml-kerberos.inst failed (exitcode: 1)
Running post-joinscripts hook(s): done