Bind 9.9 major changes

Bind 9.9 is just about to come out and I wanted to point out 1 major issue that VM might break with DNS.

By default when Bind 9.9 is installed it will convert all existing text formated zone files to a raw binary format for faster processing. This of course will throw a monkey wrench in how VM reads and writes zone changes.

Please read the following 2 sites that explain what will happen and how to prevent zone files from being converted to binary or VM will have to use a CLI to switch a zone file from binary to text on the file but I prefer the named.conf.options fix my self which is adding the line to that file which is masterfile-format text;

But you should still read up on this major change. I'm already on a debian backport version of 9.8 so for me its just around the corner.

http://geekdom.wesmo.com/2014/06/05/bind9-dns-slave-file-format/
http://lists.redbarn.org/pipermail/dnsfirewalls/2012-December/000154.html

You can also use google https://www.google.com/search?sourceid=mozclient&ie=utf-8&oe=utf-8&q=mas...

Status: 
Closed (fixed)

Comments

Howdy -- thanks for letting us know. We're looking into this now.

So does this apply to master zones as well? I know that BIND is moving to a binary format for slave zones (which Webmin already supports), but I'm surprised to hear they are going to break existing configs by changing master zones as well.

from what i gather its the master zone as well

from what i gather its the master zone as well

from what i gather its the master zone as well

I had a look, and it seems like this only applies to slave zones (which Webmin already handles binary format for)