sysquery: findns error (NXDOMAIN)

[Kevin Darcy]

You forgot to put a period on the end of the "ns1.freestates.net" A record in
your zonefile, so it was interpreted by named as an A record for
"ns1.freestates.net.freestates.net".

Either dot-terminate it, or just use the relative form, i.e.

ns1    in    a    64.232.6.186

The same problem also applies to ns2.

By the way, if ns1.centralinfo.net and ns2.centralinfo.net are slaves for
freestates.net, why aren't you listing them in the NS records for the zone?


- Kevin

ts at mttwebdesign.com wrote:

> Oct 11 11:33:32 freestates named[1082]: sysquery: findns error (NXDOMAIN) on
> ns1.freestates.net?
> Oct 11 11:34:06 freestates last message repeated 2 times
> Oct 11 11:35:24 freestates last message repeated 4 times
> Oct 11 11:35:31 freestates last message repeated 2 times
>
> Its been 7 day since I set up this nameserver so I know it has had time to
> propagate. nslookup works fine and have done all the test  to debug that are
> in the O'reilly "DNS and Bind" the kicker is that I have  another box setup
> the same way no diffence at all the same software same OS files are setup
> the same way. I have seen something on negative cashing but how do I do
> this? redhat 6.1 bind 8 p5 any clues?
> -------------------------------------------------------------
>
>                      Tom Savino
>                            CEO
>                  2Tone Web Design
>  "The Only Limitation Is The Imagination"
>                 Phone: 727-343-4426
>                      Cell: 727-481-3180
>                      Fax: 815-550-7317
>         http://www.2tonewebdesign.com
>         http://www.2tonedomains.com