Authoritative Nameserver stops resolving its own queries

[Stefan Puiu]

Seems like a resolver configuration problem, you should have the
server's address listen in its own /etc/resolv.conf file (something
like "nameserver 127.0.0.1").

This should be in a FAQ, like many others asked here I guess.=20

On 7/19/05, mworden at substantis.com <mworden at substantis.com> wrote:
> I would appreciate anyone's help in troubleshooting my problem.  I have a=
n
> authoritative nameserver (testy.substantis.com) running bind 9.3.0 on
> Fedora Core 2.  The bind install was from sources and performed according
> to the Trinity OS instructions where a chrooted version runs for both
> external and internal clients.  It works perfectly to both internal
> network clients and external clients but has suddenly stopped resolving
> its own queries including querries for which it is authoritative.  There
> have been no configuration changes and no other changes except a
>=20
> For example, dig from a client like:
> dig dumb.com @testy.substantis.com
> returns status: NOERROR
>=20
> BUT
> dig yahoo.com on a terminal on the bind server returns
> "connection timed out;  no servers could be reached."
>=20
> There are no unusual errors in /var/log/messages (i.e. ignoring
> "out-of-zone data")
>=20
>=20
>