This error is not coming from BIND, but from the startup script or wrapper.
Try running BIND manually, from a root prompt, with:
named -g -c /dev/null
If this starts, it means BIND is installed and working properly. The next step is to find out what configuration file it may be using. You can try leaving off the
-c /dev/null part and seeing what happens. If it starts, there is a config file somewhere that it found and loaded.
If no file is found, use the
-c option and point it at your
named.conf file specifically.
If those steps all work, then I would check the path that your wrapper script tries to run to ensure that it has the correct one for named.