Bug 43727 – check_essential_samba4_dns_records should check that DC=@ of _msdcs is healthy

Bug 43727 - check_essential_samba4_dns_records should check that DC=@ of _msdcs is healthy


Summary:	check_essential_samba4_dns_records should check that DC=@ of _msdcs is healthy

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:	Samba maintainers

URL:
Keywords:

Depends on:
Blocks:	43715
	Show dependency tree / graph

Reported:	2017-03-06 13:15 CET by Arvid Requate
Modified:	2019-01-03 07:21 CET (History)
CC List:	2 users (show)

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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017030221000492
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2017-03-06 13:15:49 CET

Ticket #2017030221000492 reported a case, where bind9 rejected to load the _msdcs zone. In daemon.log bind9 complained:
=====================================================================
Mar  2 17:02:31 master named[31097]: zone _msdcs.dom.local/NONE: has no NS records
Mar  2 17:02:31 master named[31097]: samba_dlz: Failed to configure zone '_msdcs.dom.local'
=====================================================================

check_essential_samba4_dns_records should check if this record is healthy.


+++ This bug was initially created as a clone of Bug #43715 +++

Comment 1 Stefan Gohmann

2019-01-03 07:21:19 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.