Bug 49529 – Allow configuration of also-notify bind parameter

Bug 49529 - Allow configuration of also-notify bind parameter


Summary:	Allow configuration of also-notify bind parameter

Status:	RESOLVED DUPLICATE of bug 37425

Product:	UCS
Classification:	Unclassified
Component:	DNS
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:	http://www.zytrax.com/books/dns/ch7/x...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-05-22 11:07 CEST by Valentin Heidelberger
Modified:	2020-09-06 10:24 CEST (History)
CC List:	3 users (show)

See Also:	48996
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:
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 Valentin Heidelberger

2019-05-22 11:07:58 CEST

Users currently can only configure the also-notify parameter for bind via a local conf or by changing the UCR template.

We should allow them to do this via UCR or via zone objects in LDAP. The latter would probably be the better approach because users might want to only notify a server about a certain zone.

Comment 1 Valentin Heidelberger

2019-05-22 11:08:51 CEST

Someone already did this via UCR btw:

https://help.univention.com/t/dns-konfiguration-notify-mechanismus-bind-also-notify/2886/2

Comment 2 Arvid Requate

2019-05-22 17:12:40 CEST


*** This bug has been marked as a duplicate of bug 37425 ***