From jsilva@kludged.com Mon May 21 10:11:12 2001
Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7])
	by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LHB6049264
	for <linux@lists.u.washington.edu>; Mon, 21 May 2001 10:11:06 -0700
Received: from porter.kludged.com (IDENT:root@porter.kludged.com [206.124.145.1])
	by mxu3.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LHB5X20595
	for <linux@u.washington.edu>; Mon, 21 May 2001 10:11:05 -0700
Received: from localhost (jsilva@localhost)
	by porter.kludged.com (8.9.3/8.9.3) with ESMTP id KAA13219
	for <linux@u.washington.edu>; Mon, 21 May 2001 10:16:21 -0700
Date: Mon, 21 May 2001 10:16:21 -0700 (PDT)
From: "Joao \"John\" Silva" <jsilva@kludged.com>
To: UW Linux Group <linux@u.washington.edu>
Subject: Re: Questions about named.
In-Reply-To: <B72E85D1.995%mweisman@gci.net>
Message-ID: <Pine.LNX.4.10.10105211013130.13183-100000@porter.kludged.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Try turning up the logging levels in your named.conf file, then
restarting named, it will probably then leave you the cause in
/var/log/messages when it barfs.

--John

On Mon, 21 May 2001, Mark on GCI Server wrote:

> Hey all,
>   I've got a DNS server up and running (well at least some of the time). It
> seems that after I load up the DNS server using the ./named restart, that
> the server stays online for a while, then comes offline again, requiring
> another restart. Any idea why this is happening? I'd like to be able to fire
> up my DNS server once, and leave it running.
> 
> Thanks,
> Mark 
> 

.