Feature changed by: Marius Tomaschewski (mtomaschewski) Feature #309036, revision 2 Title: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to - NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2-dns). + NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- + network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Marius Tomaschewski (mtomaschewski) Feature #309036, revision 5 Title: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Engineering Manager: (Novell) Developer: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) + Technical Contact: (Novell) + Technical Contact: (Novell) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Lukas Ocilka (locilka) Feature #309036, revision 7 Title: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Project Manager: (Novell) Engineering Manager: (Novell) - Developer: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Lukas Ocilka (locilka) Feature #309036, revision 10 Title: Add checkbox to yast2-dns-server whether to use NETCONFIG_DNS_FORWARDER="bind" or not openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 + Discussion: + #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) + Out of resources, please, reject. -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Lukas Ocilka (locilka) Feature #309036, revision 14 - Title: Add checkbox to yast2-dns-server whether to use - NETCONFIG_DNS_FORWARDER="bind" or not + Title: Yast DNS Server: Allow setup of forwarding DNS queries behavior openSUSE-11.3: New Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 Discussion: #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) Out of resources, please, reject. -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Lukas Ocilka (locilka) Feature #309036, revision 19 Title: Yast DNS Server: Allow setup of forwarding DNS queries behavior - openSUSE-11.3: New + openSUSE-11.3: Rejected by Lukas Ocilka (locilka) + reject date: 2013-09-12 16:04:38 + reject reason: Not done in time for openSUSE 11.3 Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 Use Case: Name server providing DNS just for external clients. Own local queries are forwarded to other servers and not resolved locally. Discussion: #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) Out of resources, please, reject. -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Lukas Ocilka (locilka) Feature #309036, revision 22 Title: Yast DNS Server: Allow setup of forwarding DNS queries behavior openSUSE-11.3: Rejected by Lukas Ocilka (locilka) reject date: 2013-09-12 16:04:38 reject reason: Not done in time for openSUSE 11.3 Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: 576759) - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 Documentation Impact: Administratin Guide, RN Use Case: Name server providing DNS just for external clients. Own local queries are forwarded to other servers and not resolved locally. Discussion: #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) Out of resources, please, reject. + #4: Lukas Ocilka (locilka) (2013-11-27 14:43:23) + Implemented in yast2-dns-server version 3.1.3 + See the whole change in this pull request + https://github.com/yast/yast-dns-server/pull/27 -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Karl Eichwalder (keichwa) Feature #309036, revision 24 Title: Yast DNS Server: Allow setup of forwarding DNS queries behavior openSUSE-11.3: Rejected by Lukas Ocilka (locilka) reject date: 2013-09-12 16:04:38 reject reason: Not done in time for openSUSE 11.3 Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - - Bug 576759 - yast dns vs. dns-server is poorly designed (feature/id: + - yast dns vs. dns-server is poorly designed (novell/bugzilla/id: 576759) + https://bugzilla.novell.com/show_bug.cgi?id=576759 - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 Documentation Impact: Administration Guide, RN Use Case: Name server providing DNS just for external clients. Own local queries are forwarded to other servers and not resolved locally. Discussion: #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) Out of resources, please, reject. #4: Lukas Ocilka (locilka) (2013-11-27 14:43:23) Implemented in yast2-dns-server version 3.1.3 See the whole change in this pull request https://github.com/yast/yast-dns-server/pull/27 -- openSUSE Feature: https://features.opensuse.org/309036

Feature changed by: Antoine Ginies (aginies) Feature #309036, revision 28 Title: Yast DNS Server: Allow setup of forwarding DNS queries behavior openSUSE-11.3: Rejected by Lukas Ocilka (locilka) reject date: 2013-09-12 16:04:38 reject reason: Not done in time for openSUSE 11.3 Priority Requester: Desirable Requested by: Marius Tomaschewski (mtomaschewski) Partner organization: openSUSE.org Description: Currently, yast2-dns-server always enables and makes use of the netconfig NETCONFIG_DNS_FORWARDER="bind" feature and writes the recursive forwarder name servers specified by the user to NETCONFIG_DNS_STATIC_SERVERS (same nameserver list as in yast2- network). This configures, that the locally running bind is used as forwarder for the system (glibc) and the bind is using the specified name servers as forwarders and allows netconfig (by default, but it depends on NETCONFIG_DNS_POLICY) to update the forwarders list via netconfig with dynamic settings, e.g. from DHCP or PPP. This behavior is usually OK, and the user can disable the updates with the DHCP/PPP/... nameservers by NETCONFIG_DNS_POLICY="STATIC" instead of "auto". But currently, yast2-dns-server does not allow to configure forwarders for e.g. non-recursive, (authorative only) name server serving some zones, without to act as forwarder/recursive name server for the local system (glibc, /etc/resolv.conf), that may use another forwarders (netconfig). To allow above configuraion, it would be required to add a checkbox to disable the current behavior and instead: * Set NETCONFIG_DNS_FORWARDER="resolver" * Write the forwardes list directly into the /etc/named.d/forwarders. conf * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") To enable current behavior again: * Reset/truncate the /etc/named.d/forwarders.conf ("cp /dev/null forwarders.conf") * Set NETCONFIG_DNS_FORWARDER="bind" * Write the forwardes list to NETCONFIG_DNS_STATIC_SERVERS * Call "netconfig update -m dns" (when it fails, ask the user whether to force and call "netconfig update -m dns -f") Relations: - yast dns vs. dns-server is poorly designed (novell/bugzilla/id: 576759) https://bugzilla.novell.com/show_bug.cgi?id=576759 - Nameserver settings of forwarders overwrite resolv.conf (novell/bugzilla/id: 561168) https://bugzilla.novell.com/show_bug.cgi?id=561168 + - yast: DNS server configuration needs better dialog design + (novell/bugzilla/id: 875014) + https://bugzilla.novell.com/show_bug.cgi?id=875014 Documentation Impact: Administration Guide, RN Use Case: Name server providing DNS just for external clients. Own local queries are forwarded to other servers and not resolved locally. Discussion: #2: Lukas Ocilka (locilka) (2011-04-13 09:43:06) Out of resources, please, reject. #4: Lukas Ocilka (locilka) (2013-11-27 14:43:23) Implemented in yast2-dns-server version 3.1.3 See the whole change in this pull request https://github.com/yast/yast-dns-server/pull/27 #8: Karl Eichwalder (keichwa) (2014-09-02 13:01:52) I tried to make sense of what's implemented but somehow failed (nevertheless I guess I mentioned everything what's available in yast). Then I entered some bugs and gave up (other things were waiting). E.g., https://bugzilla.novell.com/show_bug.cgi?id=875014 -- openSUSE Feature: https://features.opensuse.org/309036