Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using Ubuntu Server and installed BIND9 so I could set up a DNS server. I am tying to configure Reverse DNS. Here is my /etc/bind/named.conf.local file:

zone "" in{
    type master;
    file "/etc/bind/";

zone "" in{
    type master;
    file "/etc/bind/db.10.13.0.rev";

And here is my /etc/bind/db.10.3.0.rev file:

$TTL    604800
@    IN    SOA    (
                  10000                ; Serial
                  604800               ; Refresh
                  2419200              ; Expire
                  604800 )             ; Negative Cache TTL
     IN    NS
11   IN    PTR; qualified name
12   IN    PTR

The command nslookup - is producing the following:


** server can't find SERVFAIL

This is for academic purposes and I would like to know what I am doing wrong, if you could help me.

When I use named-checkzone /etc/bind/db.10.13.0.rev command, I get the following output:

dns_rdata_fromtext: /etc/bind/db.10.13.0.rev:7: near eol: unexpected end of input
zone loading from master file /etc/bind/db.10.13.0.rev failed: unexpected end of input
zone not loaded due to erros.


share|improve this question
up vote 1 down vote accepted

dns_rdata_fromtext: /etc/bind/db.10.13.0.rev:7: near eol: unexpected end of input

The error message which is included in the question says that there is an error on line 7 in the zone file. This position coincides with the end of your SOA record.

The problem is that your SOA record is missing one of its seven fields.

A SOA record has the following fields MNAME, RNAME, SERIAL, REFRESH, RETRY, EXPIRE and MINIMUM (in this order).

One of the five integer fields is missing in your SOA record, based on your comments it is the RETRY field which is missing.

share|improve this answer
The named-checkzone command returned OK now, but the nslookup command is still giving me the same error. Do you have any idea what else could be wrong? – João Rodrigues Jun 8 '14 at 16:14
Have you made bind reload the zone after fixing this? rndc reload or similar. – Håkan Lindqvist Jun 8 '14 at 16:17
Ok, my bad. I always use sudo service bind9 restart but this one time I forgot. Thank you for your time :) – João Rodrigues Jun 8 '14 at 16:25

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.