Description of problem: Because of Bug #1003972 BIND10 has to be run as root at the moment. DHCP servers create sockets by themselves and is not run as root, they don't have enough permissions to set proper socket options. Once DHCP servers are modified to use b10-socketcreator to create socket, BIND10 should be modified to run as 'named' user ("-u named"). Version-Release number of selected component (if applicable): latest How reproducible: always Steps to Reproduce: 1. cat /usr/lib/systemd/system/bind10.service Actual results: ExecStart=/usr/sbin/bind10 --pid-file /run/bind10/bind10.pid Expected results: ExecStart=/usr/sbin/bind10 -u named --pid-file /run/bind10/bind10.pid Additional info: https://lists.isc.org/pipermail/bind10-dhcp/2013-October/000043.html http://bind10.isc.org/ticket/2780 http://bind10.isc.org/ticket/3176
Resolved using setcap to gran necessary capabilities to DHCP4/6 servers.
bind10-1.1.0-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/bind10-1.1.0-6.fc19
bind10-1.1.0-11.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/bind10-1.1.0-11.fc20
Package bind10-1.1.0-11.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 bind10-1.1.0-11.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-21615/bind10-1.1.0-11.fc20 then log in and leave karma (feedback).
bind10-1.1.0-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
bind10-1.1.0-11.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.