named crashes (with nothing written to log?)

[Kevin Darcy]

Well, SERVFAIL can be any number of things. It could be a network latency
problem, where queries to all the nameservers for a domain, e.g. aol.com are
timing out.

How is your nameserver set up to resolve Internet names, by the way? If
you're using forwarding, maybe the forwarders are having problems.

You might have to turn on debug mode to get to the bottom of this problem.


- Kevin

Mark Schena wrote:

>         Hello,
> I have a problem similar to this.  I am running named 8.2.3-REL on SunOS
> 5.8.  Everything will be fine. Look-ups for authorative zones and
> non-authoratative zones work and all seems well. But,Caching for named
> will suddenly stop.  This prevents the lookups of non-authoratative zones.
> However, the zones that we have the records for still are resolved.  I
> have checked the root name servers to see if frigate.shore.net (
> our server) resolves and it does.
>
> An example of this:
> nslookup aol.com frigate
>
> Server:  frigate.shore.net
> Address:  192.233.85.129
>
> *** frigate.shore.net can't find aol.com: Non-existent host/domain
>
> I have since started and stopped named:
>
> and the same command produced:
>
> Server:  frigate.shore.net
> Address:  192.233.85.129
>
> Name:    aol.com
> Addresses:  64.12.149.24, 205.188.160.121, 64.12.149.13
>
> An nslookup -d2 aol.com
>
> produces an:
>
> Got answer (25 bytes):
>     HEADER:
>         opcode = QUERY, id = 38116, rcode = SERVFAIL
>         header flags:  response, want recursion, recursion avail.
>         questions = 1,  answers = 0,  authority records = 0,  additional =
> 0
>
> The logs for debugging show nothing unusual.  I am at a loss as where to
> go next.  Oh, I have checked with networksolutions and the domains are
> paid up to date.
>
>         Any suggestions?
>         At this point I am willing to do just about anything short of
> human sacrifice.
>         Thanks and regards,
>
> Mark Schena         mschena at primushost.com