Bug 1070631

Summary: NetworkManager dispatcher script doesn't respect nameserver list changes
Product: [Fedora] Fedora Reporter: Pavel Šimerda (pavlix) <psimerda>
Component: dnssec-triggerAssignee: Pavel Šimerda (pavlix) <psimerda>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: pspacek, pwouters, thozza, vonsch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnssec-trigger-0.12-13.fc20 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-19 10:06:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1100796    
Bug Blocks:    

Description Pavel Šimerda (pavlix) 2014-02-27 09:53:27 UTC
The dispatcher script only checks whether Unbound has a specific zone configured already, and if yes, doesn't check whether it contains the same data as the connection. When for example the connection name server list is changed, this change is not propagated to Unbound.

Comment 1 Pavel Šimerda (pavlix) 2014-03-19 10:56:09 UTC
Just filed a related upstream bug report:

https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=567

Comment 2 Pavel Šimerda (pavlix) 2014-06-06 15:06:03 UTC
The dnssec-script part fixed in 0.12 except that bug #1100796 was introduced. The unbound part fixed upstream but not ported to Fedora.

Comment 3 Pavel Šimerda (pavlix) 2014-06-06 17:23:07 UTC
I want to track this for F20 instead. The blocker is fixed in rawhide. Unbound part is tracked by bug #1067856 but we don't strictly depend on it.

Comment 4 Pavel Šimerda (pavlix) 2014-06-06 17:23:32 UTC
Fixed in rawhide, will update F20 when ready.

Comment 5 Fedora Update System 2014-06-30 15:29:55 UTC
dnssec-trigger-0.12-12.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-12.fc20

Comment 6 Fedora Update System 2014-07-01 07:21:34 UTC
Package dnssec-trigger-0.12-12.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnssec-trigger-0.12-12.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7942/dnssec-trigger-0.12-12.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-08-11 11:40:37 UTC
dnssec-trigger-0.12-13.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-13.fc20

Comment 8 Fedora Update System 2014-09-19 10:06:56 UTC
dnssec-trigger-0.12-13.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.