What does the error mean?
BIND is a program that runs DNS on a server. DNS is like a phone book for the internet. BIND reads its settings from a file called named.conf. This error means BIND looked for that file and could not find it. Like a cook who lost the recipe, it cannot start.
Why does it happen?
- The file was deleted or renamed by mistake.
- BIND was installed, but the config file was never created.
- The file is in a different folder on your system. On Debian or Ubuntu, it is often
/etc/bind/named.conf. - The file was moved while BIND runs in a chroot. A chroot is a locked-away folder where BIND runs for safety.
/etc files first.Steps
- Log in to your server with SSH as root.
- Check whether the file exists.
ls -l /etc/named.conf
This lists the file if it is there.
- Search the whole server for it.
find / -name "named.conf*" 2>/dev/null
This looks for any file with that name. The part at the end hides permission noise.
- If you find a copy in another folder, point BIND to it, or copy it into place.
cp /etc/bind/named.conf /etc/named.conf
This copies the file to where BIND expects it. Change the first path to the one you found.
- If no file exists, reinstall the package. On AlmaLinux, Rocky or CentOS, use this.
yum reinstall bind
This puts the default files back. Use apt install --reinstall bind9 on Ubuntu or Debian.
- Check the file for mistakes.
named-checkconf /etc/named.conf
This prints errors if the file has any. No output means it looks fine.
- Restart BIND.
systemctl restart named
This starts the service again. On Ubuntu it may be called bind9.
Control panel servers
If you use cPanel, DirectAdmin or Plesk, the panel writes this file for you. Use the panel's own DNS rebuild option instead of hand-editing. You can open a support ticket if you are unsure.
Quick recap
- BIND cannot start without
named.conf. - Check whether the file exists or sits in another folder.
- Copy it, or reinstall the BIND package.
- Test with
named-checkconf, then restart. - Back up before you change anything.