These are nameservers that do NOT answer authoritatively for your domain

Posted on 2004-11-27
Last Modified: 2008-01-09

I am running 2 nameservers for my domain

box1 ( is running an old version of slackware and bind 8.1.2
box2 ( is running slackware 9, and bind 9.2.2 p3

When I run dnsreport against my domain, I get the following error related to my primary, which is box1. "These are nameservers that do NOT answer authoritatively for your domain"

Here is my named.conf file from the bind 8.1.2 machine, but it the same on the other server. I added the auth-nxdomain yes; to the options, but this did not help, athough it fixed the problem on the bind 9.2.2 box.

arial:~# cat /etc/named.conf
 * A simple BIND 8 configuration

options {
        directory "/var/named";
        auth-nxdomain yes;
       multiple-cnames no;
zone "." {
         type hint;
         file "";
zone "" {
        type master;
        file "zone/";
zone "" {
        type master;
        file "zone/";
zone "" in {
        type master;
        file "zone/named.local";

any suggestions?

Question by:tagish
    LVL 38

    Expert Comment


       In your zone file "zone/", how many nameservers listed for your domain ""?
    I mean for example:
    $TTL 86400
    @ IN SOA (
    2004041905 ; Serial (yyyymmddxx format)
    10800 ; Refresh 3 hours
    3600 ; Retry 1 hour
    604800 ; Expire
    86400 ) ; Default_ttl 24 hours

    @ IN NS   <=== How many "@ IN NS ......" in "zone/" file
    @ IN NS   <===
    I check the dnsreport with your domain and only saw 2 nameservers are registered.

    If you have more than 2 nameservers in zone/, then you will get "lame server" failure on dnsreport.
    Either you register "" as your nameserver or simply take it out from the zone file.



    Author Comment

    I have only 2 name servers currently. I have not set them up to be master/slave's, as I was hoping both would be authoratative, and could do a manual update of the zone files as needed...

    My zone file is as follows on the primary (
    arial:~# cat /var/named/zone/
    #$ttl 38400 IN      SOA (
                            2004112601      ;serial
                            7200            ;refresh
                            7200            ;retry
                            3w              ;expiry
                            86400 )         ;min
                            NS  ;
                            NS  ;
                            MX       10;

    localhost               A              ;   IN      A
                            HINFO   "PC"    "LINUX"         ;     IN      A
                            HINFO   "linux" "SERVER"        ;     IN      A   ;     IN      A   ;   IN      RP resperson;   IN      A
                            HINFO    "LINUX" "SERVER"       ;

    LVL 2

    Accepted Solution

    The error is just a warning to you - the problem is with the
    machine that in.named is reporting to. It is delegating authority
    for one of it's subdomains to a machine which is not lower in the
    DNS hierarchy.

    Do a master/slave hierarchy and be sure that both of them will be authoritative it *might* solve the question


    Author Comment


    I am going to accept Marcin's answer. It makes sense, and fits with some other reading I have been doing. My plan was to make my server a master and have it update a slave at a different location (right now they sit one on top of the other :-) ). I will make that change sooner now and see what happens rather than change the config on my current machine that will be turned off soon.


    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    Suggested Solutions

    I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
    Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
    It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
    This video discusses moving either the default database or any database to a new volume.

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now