Bug 17668 – Anlegen einer "type forward" DNS-Zone

Bug 17668 - Anlegen einer "type forward" DNS-Zone


Summary:	Anlegen einer "type forward" DNS-Zone

Status:	RESOLVED WONTFIX

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

Importance:	P3 enhancement with 2 votes (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Duplicates:	19511 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-02-16 14:46 CET by Janis Meybohm
Modified:	2019-01-03 07:20 CET (History)
CC List:	12 users (show)

See Also:	47176
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.091
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2010021610000321, 2011041510006536, 2013072521000921, 2014040821001626, 2014041421005432, 2010021610000321, 2016031021000353
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 Janis Meybohm

2010-02-16 14:46:52 CET

Ticket 2010021610000321


Es sollte möglich sein eine "type forward" DNS-Forward-Zone im UDM anzulegen. 

Bsp:

root@one:~# cat /etc/bind/local.conf.proxy
# add local zones here
zone "externe-zone.orig" {
        type forward;
        forwarders {10.200.6.30;};
};

Comment 1 Murat Odabas

2011-04-19 09:46:58 CEST

Wurde erneut angemerkt, Ticket Nr.: 2011041510006536

Comment 2 Stefan Gohmann

2011-12-21 14:28:26 CET

*** Bug 19511 has been marked as a duplicate of this bug. ***

Comment 3 Dirk Ahrnke 2013-05-24 12:26:37 CEST

weitere Anfrage in http://forum.univention.de/viewtopic.php?f=48&t=2632

Comment 4 Janis Meybohm

2013-07-25 10:13:24 CEST

Erneut angefragt: Ticket#: 2013072521000921

Comment 5 Ingo Steuwer

2014-04-14 08:37:32 CEST

wieder angefragt über 2014040821001626

Comment 6 Ingo Steuwer

2014-04-14 13:44:57 CEST

requested by 2014041421005432

Comment 7 Michel Smidt 2014-04-22 13:41:06 CEST

For your information: Bug #34601 about a cool solution for DNS forwarding with "type forward" DNS-zones and subdomains

Comment 8 Stefan Gohmann

2015-12-04 11:56:37 CET

Requested again Ticket #2015120321000521.

Comment 9 Florian Best

2016-03-10 12:34:03 CET

Requested again Ticket #2016031021000353.

Comment 10 Florian Best

2016-03-10 12:51:38 CET

Should this be a LDAP entry or UCR variables?

Comment 11 Arvid Requate

2016-03-10 14:02:56 CET

LDAP entry, handled by bind.py Listener.

Comment 12 Florian Best

2016-03-10 14:14:47 CET

So we should create a new UDM handler dns/forward_zone_type_forward with a multivalue property "forwarders"? Or just modify the dns/forward_zone handler: add a property 'type' (defaulting to 'master', changeable to master | slave | stub | hint | forward | delegation-only) plus that "forwarders" property (which then has no effect for type!=forward).

The named.conf manpage isn't really verbose about what configuration settings can be done for type='forward'-zones.

Comment 13 Philipp Hahn

2016-08-26 18:09:19 CEST

Asked for during UCS Technical training 2016-08 Task #4773

Comment 14 Philipp Hahn

2018-03-09 15:07:36 CET

Make sure to understand <https://deepthought.isc.org/article/AA-00538/0> when adding a "forward" zone!

Comment 15 Stefan Gohmann

2019-01-03 07:20:33 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.