Stephane Bortzmeyer <bortzme...@nic.fr> wrote, in part:
>The problem (NS going to CNAME) was properly identified by Hauke Lampe
>very soon in the thread. Read it.
>
>> "Unable to find primary nameserver (SOA)"
>
>Well, the error message could be better, that's sure...
There are a number of reasons why the SOA could not be located:
NS pointing to a CNAME,
incorrect NS delegation from the parent,
lame server,
name server not accessible from the Internet,
etc.
If the zonecheck code is able to determine what the reason is, then
it should give the reason. I was looking for incorrect delegation or
inaccessible name server. I did not notice the CNAME. This zone
is maintained by a different group here; all I do is slave the zone.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone: +1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 222, Room D209 Internet: bsfin...@anl.gov
Argonne, IL 60439-4828 IBMMAIL: I1004994
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
