This is a tracking bug for Change: BIND version 9.10
For more details, see: https://fedoraproject.org//wiki/Changes/BIND_9.10
BIND (Berkeley Internet Name Domain) version 9.10 is the latest stable major update of the widely used DNS server. Besides new features, some settings defaults have changed since the previous major version (9.9).
Bind has been updated:
Dependent packages has been rebuilt:
dhcp - http://koji.fedoraproject.org/koji/buildinfo?buildID=603863
bind-dyndb-ldap - http://koji.fedoraproject.org/koji/buildinfo?buildID=603865
dnsperf - http://koji.fedoraproject.org/koji/buildinfo?buildID=603866
This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 .
At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.
This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon.
In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.
Moving to MODIFIED, as the change is complete in F22+. However last week we discovered a problem with DHCP server and client.
BIND 9.10 comes with redesigned shared libraries against which DHCP is built. ISC bundles the BIND sources in the DHCP source archive, however to conform with Fedora packaging guidelines we are deleting these from the archive and are building DHCP using BIND libraries from Fedora.
Now the issue is that DHCP built against BIND 9.10 version does not work at all. We discussed this with DHCP and BIND upstream. They acknowledged that the effort was never finished in DHCP due to lack of time, however they currently don't have any plan (and estimate) on when this could be fixed. 
So we have three possibilities:
1. There seems to be a temporary workaround if libdns and libisc is built with --disable-epoll and --disable-threads. This would require tweaking BIND's Makefile to build a special versions of libdns and libisc just for DHCP and then link DHCP against these. Downside is that although this makes DHCP server and client work in the background, the only way to stop them is by 'kill -9'.
2. Ask FPC for an exception to build DHCP against the bundled BIND sources and ship latest major version of BIND in Fedora.
3. Revert the changes, bump epoch of BIND and ship only BIND 9.9 version in Fedora and keep DHCP as is.
I forgot to add the upstream discussion thread to the previous comment...
(In reply to Tomas Hozza from comment #3)
> So we have three possibilities:
> 1. There seems to be a temporary workaround if libdns and libisc is built
> with --disable-epoll and --disable-threads. This would require tweaking
> BIND's Makefile to build a special versions of libdns and libisc just for
> DHCP and then link DHCP against these. Downside is that although this makes
> DHCP server and client work in the background, the only way to stop them is
> by 'kill -9'.
This possibility turned up to be NOT doable. I was not able to successfully modify BIND in such a way to build also special version of libraries, that ISC DHCP would be able to run with.
Created FPC ticket for DHCP:
COPR build of DHCP created by Jiri Popelka:
This message is a reminder that Fedora 22 "Change Checkpoint: 100% Code Complete Deadline" is on 2015-03-31 .
All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.
As for several System Wide Changes, Beta Freeze is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2015-04-01 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).
The change is live in F22+. All issues resolved. Switching to ON_QA.