Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I noticed that a month or two ago that my bind records for the slave server became unreadable. The consequence of having an unreadable record is that it appears as though Webmin cannot read the record. I used to be able to go into Webmin on the slave machine to validate that the record was updated there, I can no longer do that.

It appears to still be a valid record because I can query the server itself and it returns the same data (NSLOOKUP, etc). So it appears as though Bind can read the file fine.

I would like this resolved, but I'm not sure where to look. Any thoughts?

Here is are the the master and slave records:

BIND version 9.8.4
Debian Linux 7

$ttl 38400
servertest.com. IN  SOA testdns.com. foobar.testdns.com. (
        38400 )
servertest.com. IN  NS  ns1.testdns.com.
servertest.com. IN  NS  ns2.testdns.com.

BIND version 9.9.2
Ubuntu Linux 13.04

^\ ^@^@^N^P^@^Ru^@^@^@~V^@^@^@^@J^@^A^@^B^@^@^@^@~V^@^@^@^@^B^@^P

All the details are there, but the slave is unreadable. (copy and pasted from PuTTy

share|improve this question

1 Answer 1

up vote 0 down vote accepted

They are unreadable by default since BIND version 9.9.

Here is how you can make it readable:

# convert raw zone file "example.net.raw", containing data for zone example.net,
# to text-format zone file "example.net.text"

named-compilezone -f raw -F text -o example.net.text example.net example.net.raw

# convert text format zone file "example.net.text", containing data for zone
# example.net, to raw zone file "example.net.raw"

named-compilezone -f text -F raw -o example.net.raw example.net example.net.text


share|improve this answer
Excellent. That's what I needed to know. –  Foobar Aug 22 '13 at 15:13

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.