BIND Update blew out all DNS zone files

7 posts / 0 new
Last post
#1 Thu, 11/17/2011 - 07:19

BIND Update blew out all DNS zone files

I did the update about ten hours ago which updated BIND, and it blew out all of my DNS! If I go to server configuration, DNS Records, I get

No zone file found for

and I have no ability then to edit the 'non-existent' DNS!

When I try to make a new zone file for an existing domain on my server, I get

Failed to create master zone : File /var/lib/bind/ already exists

How to I correct all this? Both of my servers are affected and every domain is now offline.

Thu, 11/17/2011 - 09:23


Yeah, a BIND update definitely shouldn't affect your existing DNS zones!

I'm curious what output you get if you run this command:

find /var -name

Whenever it finds the file(s), take a look at it -- does it contain the correct DNS records?


Thu, 11/17/2011 - 09:37

Well, the zone files are in /var/lib/bind where they should be, but the /etc/bind/named.conf.local file is basically empty.

I have done one server so far by editing /etc/bind/named.conf.local manually to include a couple of dozen zone files.

Thu, 11/17/2011 - 10:06

Yeah, that's nuts that there's a time when the BIND package can overwrite that file, that certainly shouldn't ever happen.

However, unless you have a backup of your config files -- what you're doing now is probably the best way to get that up and running again.


Tue, 02/11/2014 - 13:51

I believe this just happened to me also. I have backups would it be safe to just restore the DNS Backups? I am not sure how my DNS is still functioning because I see "No zone file found for" for all my virtual servers.

Tue, 02/11/2014 - 13:52

This also seems to cause all backups to show that they partially fail.

Tue, 02/11/2014 - 13:56

If any of the files in /etc/bind or /var/lib/bind don't contain anymore what they should, it should be safe to restore specifically those files from a backup.

Topic locked