Bug 56993 - 98univention-samba4slavepdc-dns.inst fails, caused by a manual adjusted resolv.conf
98univention-samba4slavepdc-dns.inst fails, caused by a manual adjusted reso...
Status: NEW
Product: UCS
Classification: Unclassified
Component: Join (univention-join)
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2024-01-19 15:32 CET by Christina Scheinig
Modified: 2024-01-19 15:32 CET (History)
0 users

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2024011821000265
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 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