I’ve just upgraded to 12.1 (64bit) named will not start via the init script which sends.
start_daemon -p /var/lib/named /var/run/named/named.pid /usr/sbin/named -t /var/lib/named -u named
I can start named as root with no options but it fails with the -t option.
Any ideas.
After attempting to start, check “/var/log/messages” (near the end of that logfile) for any logged errors.
I haven’t run it for a while. As I recall, when starting “/etc/named.conf” is copied to “/var/lib/named/etc/” before starting. Make sure that there is a good “named.conf” in that directory.
I don’t understand what has happened but it’s starting now.
I installed bind on my desktop which is also 12.1 and it started without problem. I noticed something in the changelog for bind about apparmor and wondered if there were still some problems there. My desktop wasn’t running this but the other one was.
I stopped apparmor on this and tried to start bind via the init script. It started up. I then tried to stop and start again with apparmor running this time and although I wasn’t expecting it to, bind started OK and has since started on a reboot.