SERVFAIL - need advice on diagnosing

[Ronald Landheer]

OK, so there's no difference between the two servers except that one
fails and the other doesn't?
/etc/resolv.conf is the same?
/etc/named.conf is the same (you just told me so)

hmm..

If resolv.conf is not it either, I suggest posting the config and
letting the gurus (NOT me) take a look at it - that's what I did :)

I should say I'm no wiz at bind: I stick around on helpful lists to
learn and be helpful when I've had similar problems (least I can do)

The only files of importance I know of (other than basic network config,
which would make your problem obvious & one of many) are
/etc/resolv.conf, /etc/named.conf, /etc/hosts and /var/named/* (the zone
files). If BIND is failing, it's either this, or someone is teasing you.

Good luck :)

Ronald
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of Whit Blauvelt
> Sent: woensdag 28 november 2001 16:44
> To: Ronald Landheer
> Cc: bind-users at isc.org
> Subject: Re: SERVFAIL - need advice on diagnosing
>
>
>
> Ronald,
>
> Thanks for the advice. I just ran "diff" on the named.conf in the failing
> server and its working twin, and the file is identical - so that's not the
> problem. Also, as I mentioned before, "There is nothing showing up in the
> logs." Aside from updating bind to stay ahead of security concerns, it's
> worked reliably for me for years. I'm still hoping someone can point me
> towards a methodology for diagnosing the current failure.
>
> Whit
>
> On Wed, Nov 28, 2001 at 09:08:01AM +0100, Ronald Landheer wrote:
> >
> > I recently had the same kind of problem - there was a missing semicolon
> > in my named.conf file. You might want to check that.
> > Other than that, logs are a nice place to look :)
> >
> > Greetz!
> >
> > Ronald
> >
> > > -----Original Message-----
> > > From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> > > Behalf Of Whit Blauvelt
> > > Sent: dinsdag 27 november 2001 21:41
> > > To: bind-users at isc.org
> > > Subject: SERVFAIL - need advice on diagnosing
> > >
> > >
> > >
> > > Hi,
> > >
> > > I have bind 9.1.1 (compiled from source) running identically
> on two Debian
> > > Linux systems. One is literally a clone of the other, except with a
> > > different public connection. Both are identically configured
> as secondary
> > > DNS for a couple of domains. Both were working fine until
> > > recently. Now, one
> > > of them is doing "SERVFAIL" instead, whether accessed locally
> or remotely.
> > > Like:
> > >
> > > # dig @localhost some.com
> > >
> > > ; <<>> DiG 9.1.1 <<>> @localhost some.com
> > > ;; global options:  printcmd
> > > ;; Got answer:
> > > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44692
> > > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
> > >
> > > ;; QUESTION SECTION:
> > > ;some.com.               IN      A
> > >
> > > ;; Query time: 1 msec
> > > ;; SERVER: 127.0.0.1#53(localhost)
> > > ;; WHEN: Tue Nov 27 15:38:22 2001
> > > ;; MSG SIZE  rcvd: 33
> > >
> > > There is nothing showing up in the logs, and I can't find anything on
> > > SERVFAIL in the docs except for an RFC that has nothing much
> to do with
> > > diagnosis. The named daemon is running, it's just
> SERVFAILing. What are
> > > useful diagnostic steps? Is there a guide somewhere?
> > >
> > > Thanks,
> > > Whit


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com