As the summary says, if the network is down when named starts, all requests will be rejected once it is up. This is of course the norm now that we have NM. I can't really figure out why it refuses the lookups though. It listens to 0.0.0.0 and my configuration doesn't have any restrictions on who can do lookups, so it shouldn't need a network connection to start properly.
As a temporary workaround, I suggest this be added to dispatcher.d: [root@freyr dispatcher.d]# cat /etc/NetworkManager/dispatcher.d/10-named #!/bin/sh export LC_ALL=C if [ "$2" = "up" ]; then killlall -HUP named fi It solves the problem and should not have any serious consequences.
I improved your script a little, it will be in the next update. #!/bin/bash # Check if named is running /sbin/service named status > /dev/null 2>&1 || exit 0 [ "$2" = 'up' -o "$2" = 'down' ] && /sbin/service named reload
bind-9.6.1-5.P1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/bind-9.6.1-5.P1.fc11
bind-9.6.1-5.P1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bind'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9677
bind-9.6.1-6.P1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.