Lame DNS server

bind

I'm trying to setup my BIND with a domain I own and I'm using dnssy.com and intodns.com to check if everything is ok, but I'm getting errors in both. The error says that my DNS server is "lame" (which I don't understand what does it mean).

My named.conf

options {
    directory "/var/dns";
    pid-file "/var/run/named/named.pid";
    auth-nxdomain yes;
    datasize default;
    listen-on-v6 { any; };
    listen-on { 127.0.0.1; 188.165.234.51; };
    listen-on-v6 { ::1; };
    allow-recursion { 127.0.0.1; };
    allow-transfer { none; };
    allow-update { none; };
    allow-query { any; };
    allow-query-cache { any; };
    version none;
    hostname none;
    server-id none;
};
include "/var/dns/autogen-zones";

autogen-zones is an autogenerated file which contains the following:

zone "localhost" IN {
     type master;
     file "localhost.zone";
     allow-transfer { any; };
};
zone "0.0.127.in-addr.arpa" IN {
     type master;
     file "127.0.0.zone";
     allow-transfer { any; };
};
zone "." IN {
     type hint;
     file "root.hint";
};
zone "destinosxures.com" IN {
     type master;
     file "destinosxures.com.zone";
     allow-query { any; };
     allow-transfer { any; };
};

Last, my destinosxures zone:

$TTL 604800
@ IN SOA ns367310.ovh.net. hostmaster.destinoxures.com. (
  2012030503   ; Serial yyyy/mm/dd/id
       10800   ; Refresh
        3600   ; Retry
     604800   ; Expire
      10800 ) ; Negative Cache TTL

@ IN NS    ns367310.ovh.net.
@ IN NS    sdns2.ovh.net.

ns1     IN A 188.165.234.51
ns2     IN A 188.165.234.51
@       IN A 188.165.234.51
www     IN A 188.165.234.51

http.tcp SRV 0 3 80 destinoxures.com.
https.tcp SRV 1 0 443 destinoxures.com.

Oh, by the way, my resolv.conf has:

nameserver 127.0.0.1
nameserver 213.251.188.141

What is wrong with my config?

Regards

Your named.conf lists the zone as destinosxures.com while the zonefile itself refers only to destinoxures.com (note missing central "s"). If that reflects what's really on your server, then it's definitely a problem.

And may I in passing thank you for not obscuring the domain name in the question; if you had, we'd likely never have found the answer. Others who are posting questions, particularly DNS questions, please take note.

Lame DNS server

Related

Recent Posts