Description of problem: Upgraded nsd from updates. nsd starts, but due to ownership of /etc/nsd - it has permission problems reading zone files. Changed to nsd:nsd to fix that. Big problem is that it no longer actually serves or distributes zone information to slaves. Version-Release number of selected component (if applicable): 4.1.7 How reproducible: always Steps to Reproduce: 1. Upgrade 2. Realize you can't resolve your domain 3. Scream silently Actual results: Failed domain resolution Expected results: Upgrade that works Additional info: Slave reports complaints of zone ... received error code NOT IMPL from master zone ... received error code SERVER NOT AUTHORITATIVE FOR ZONE from master_IP zone ... from master: no tsig in first packet of reply Master additionally reports error: /var/lib/nsd/nsd.db: wrong type of file along with the permission errors, but correcting the ownership of /etc/nsd seemed to make that go away as well - master starts and restarts without error - it just won't serve information via nslookup on it. Restoring the previous F22 version of the NSD package returns the system to normal operation.
Upgrading from what version-release to what version-release? Something like this may show you which revision you had before and after upgrading: sudo dnf history info nsd |grep nsd
From the previous released working version for f22 nsd-3.2.18-2.fc22.x86_64
Wiping out the database and restarting from text files created a proper database on F23 - so the only issue would be upgrade between versions.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.