Univention Bugzilla – Bug 56993
98univention-samba4slavepdc-dns.inst fails, caused by a manual adjusted resolv.conf
Last modified: 2024-01-19 15:32:17 CET
The samba_dnsupdate part in the 98univention-samba4slavepdc-dns.inst fails, even after an univention-join. The script states, that the record is already there, but this might be not the right one. So three time already the resolv.conf was manual adjusted, ERROR(runtime): Record already exists; record could not be added. zone[schein.me] name[@] [WERR_DNS_ERROR_RECORD_ALREADY_EXISTS] - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') ERROR(runtime): Record already exists; record could not be added. zone[_msdcs.schein.me] name[@] [WERR_DNS_ERROR_RECORD_ALREADY_EXISTS] - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') ERROR(runtime): Record already exists; record could not be added. zone[schein.me] name[@] [WERR_DNS_ERROR_RECORD_ALREADY_EXISTS] - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') ERROR(runtime): Record already exists; record could not be added. zone[schein.me] name[_ldap._tcp] [WERR_DNS_ERROR_RECORD_ALREADY_EXISTS] - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') And a ucr commit solved the resolved.conf. We should do an ucr commit /etc/resolv.conf in the univention-join