Server Not Authoratative

[Eric Pancer]

On 9/13/05, Stefan Puiu <stefan.puiu at gmail.com> wrote:
> 
> I think that you should get a SERVFAIL for the zone if the server tried to 
> load it and failed, so I'd rather look in your named.conf file and see if 
> you have the "catastrophe.net <http://catastrophe.net>" zone there at all. 
> 

Looks like I have it working; it seemed to be an issue with cname's and 
views. Seems as though bind won't claim to be authoratative if you have a 
cname pointing to a cname in a view. Fine by me - I just deleted it.

My only other question is that I'm seeing a whole bunch of 

Sep 13 00:58:26 ictus named[14452]: createfetch: 
195.243.227.207.in-addr.arpa PTR
Sep 13 00:58:26 ictus named[14452]: client 207.227.243.194#19047: view 
internal:
query: 195.243.227.207.in-addr.arpa IN PTR -E
Sep 13 00:58:26 ictus named[14452]: lame server resolving '
195.243.227.207.in-add
r.arpa' (in '195.243.227.207.in-addr.arpa'?): 207.227.243.194#53

This is happening across ns1 and ns2 for my domain. I *know* that these 
servers are configured to be authoritative now. Is there a reason that using 
a configuration with views would make this occur more? I can post my configs 
if necessary.

Thanks.