Server Not Authoratative
Mark Andrews
Mark_Andrews at isc.org
Tue Sep 13 06:22:54 UTC 2005
> 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.
Named doesn't care about CNAMEs pointing to CNAMEs. You
have misdiagnosed the problem.
> 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.
>
>
227.207.in-addr.arpa. 86400 IN NS ns2.level3.net.
227.207.in-addr.arpa. 86400 IN NS ns1.level3.net.
;; Received 92 bytes from 192.41.162.32#53(epazote.ARIN.NET) in 215 ms
243.227.207.in-addr.arpa. 86400 IN NS pulmonary.ispfh.org.
243.227.207.in-addr.arpa. 86400 IN NS peabody.cultural.com.
;; Received 145 bytes from 209.244.0.2#53(ns2.level3.net) in 167 ms
195.243.227.207.in-addr.arpa. 86400 IN NS A.NS.NXIO.US.
;; Received 88 bytes from 207.227.240.1#53(pulmonary.ispfh.org) in 1032 ms
195.243.227.207.in-addr.arpa. 7200 IN PTR a.mx.nxio.us.
243.227.207.in-addr.arpa. 7200 IN NS ns1.nxio.us.
;; Received 90 bytes from 2001:4830:2280::53#53(A.NS.NXIO.US) in 244 ms
Well A.NS.NXIO.US is supposed to be serving
195.243.227.207.IN-ADDR.ARPA acording to PULMONARY.ISPFH.ORG
but is not configured to serve it based on the last answer
above. Instead it is serving 243.227.207.IN-ADDR.ARPA.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews at isc.org
More information about the bind-users
mailing list