Bug 36039 - Setup and nameserver handling
Setup and nameserver handling
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: DNS
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.0
Assigned To: Stefan Gohmann
Felix Botner
: interim-2
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-02 07:28 CEST by Stefan Gohmann
Modified: 2014-11-26 06:53 CET (History)
0 users

See Also:
What kind of report is it?: ---
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?:
ISV affected?:
Waiting Support:
Ticket number:
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 Stefan Gohmann univentionstaff 2014-10-02 07:28:21 CEST
Currently, a new installed DC master uses it's on IP as nameserver. That' OK. But the nameserver given by the installation should be used as forwarder. At the moment it becomes the seconds nameserver.
Comment 1 Stefan Gohmann univentionstaff 2014-10-02 07:38:16 CEST
90univention-bind-post.inst now does a simple mapping: r54135

Changelog: r54136
Comment 2 Felix Botner univentionstaff 2014-10-02 17:34:23 CEST
OK - dns/forwarder[1-3] (if empty) is set to value of nameserver[1-3] are 
OK - after installing a master system with nameserver 192.168.0.3 i got

nameserver1: 10.200.7.83
nameserver2: 192.168.0.3
dns/forwarder1: 192.168.0.3

OK - Changelog
Comment 3 Stefan Gohmann univentionstaff 2014-11-26 06:53:58 CET
UCS 4.0-0 has been released:
 http://docs.univention.de/release-notes-4.0-0-en.html
 http://docs.univention.de/release-notes-4.0-0-de.html

If this error occurs again, please use "Clone This Bug".