Bug 32131 - "not authoritive"-messages in daemon.log of Samba4 DCs
Summary: "not authoritive"-messages in daemon.log of Samba4 DCs
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: DNS
Version: UCS 3.1
Hardware: Other Linux
: P5 minor
Target Milestone: ---
Assignee: UCS maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-30 16:13 CEST by Ingo Steuwer
Modified: 2018-04-13 13:32 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.006
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID: 08418
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 Ingo Steuwer univentionstaff 2013-07-30 16:13:53 CEST 
Seen with UCS 3.1-1 Errata 156 in an environment with UCS DCs with and without Samba4

On Samba4 DCs we see messages like this in daemon.log on Samba4 DCs:

Jul 29 01:03:01 myhostname named[3048]: client <IP of Non-Samba4-DC>#1207: received notify for zone 'my.domain': not authoritative

The messages are repeated unregularly and with different <IP of Non-Samba4-DC>. I'd assume problems with the DDNS here?

There is no known issue -> Sverity:minor
Comment 1 Philipp Hahn univentionstaff 2017-04-19 08:17:27 CEST 
BIND sends NOTIFY messages to all NS of a zone, although they are only needed between the LDAP-named and PROXY-named (or when external NS are used). See Bug #44380 for more details.
We can/should disable sending NOTIFY by default.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:36:33 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Florian Best univentionstaff 2017-06-28 14:52:39 CEST 
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 4 Stefan Gohmann univentionstaff 2017-08-08 07:09:56 CEST 
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.