From owner-freebsd-current Thu May 7 07:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17773 for freebsd-current-outgoing; Thu, 7 May 1998 07:10:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17748 for ; Thu, 7 May 1998 07:10:07 -0700 (PDT) (envelope-from mike@ns1.seidata.com) Received: from localhost (mike@localhost) by ns1.seidata.com (8.8.8/8.8.5) with SMTP id KAA08911; Thu, 7 May 1998 10:09:49 -0400 (EDT) Date: Thu, 7 May 1998 10:09:49 -0400 (EDT) From: Mike To: Dennis Tenn cc: FreeBSD Current Subject: Re: cvsup as of May 6th and named. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 7 May 1998, Dennis Tenn wrote: > Can someone explain why nameservice isn't working now that I've cvsuped > the latest source as of May 6th, 1998 and rebuilt all the binaries and a Just a wild thought (since I haven't cvsupped myself lately)... I know I saw discussion about updating BIND to 4.9.7 (2.2.x) and 8.1.2 (3.0). Did you cvsup to 3.0 and get BIND 8.1.2? If so, is /etc/rc.conf updated to point the named flags to named.conf instead of named.boot? Does named start but just not 'work' or does it not even start? If it starts, doing an 'ndc reload;tail /var/log/messages' should give you some useful info. Assuming it is a simple config file error or something similar, named should output its complaint(s) to messages. -mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message