From: AITGW::"munroe@dmc.com" "Dick Munroe" 29-MAR-1992 13:48:21.74 To: mccall!cmu-tek-newsgate CC: Subj: Re: Trouble with the Domain Server (I think) Received: by AITGW.DECnet (utk-mail11 v1.5) ; Sun, 29 Mar 92 13:46:57 EST Received: from CMUTEK.CC.CMU.EDU by aitgw.ge.com (5.65/GE Gateway 1.5) id AA00386; Sun, 29 Mar 92 13:46:53 -0500 Errors-To: SYNFUL@CMUTEK.CC.CMU.EDU X-Listname: CMU-TEK TCP/IP Mailing list Received: from depot.cis.ksu.edu by CMUTEK.CC.CMU.EDU (MX V3.0A) with SMTP; Mon, 23 Mar 1992 16:52:08 EST Return-Path: Received: from mccall.UUCP by depot.cis.ksu.edu UUCP (5.65a) id AA09953; Mon, 23 Mar 92 15:53:17 -0600 Received: by mccall.com (DECUS UUCP /1.3-1/2.5/); Mon, 23 Mar 92 15:46:23 CST To: mccall!cmu-tek-newsgate Subject: Re: Trouble with the Domain Server (I think) Message-Id: <1992Mar23.121456.4235@dmc.com> From: munroe@dmc.com (Dick Munroe) Reply-To: munroe@dmc.com (Dick Munroe) Date: 23 Mar 92 12:14:56 EST Organization: Doyle Munroe Consultants, Inc., Hudson, MA In article <1992Mar17.184528.4215@dmc.com>, munroe@dmc.com (Dick Munroe) writes: Well, I managed to get the problem to go away, but what I did is a little counter-intuitive. 1. I added an initial record to the DOMAIN$SERVER_STARTUP file: -------------------------------------------------------------------------------- ; Startup file for domain server primary dmc.com domsdir:dmc-com.zone_master primary 1.1.192.in-addr.arpa domsdir:1-1-192.zone_master initial domsdir:initial.dat -------------------------------------------------------------------------------- The initial file contained: -------------------------------------------------------------------------------- ; RR's to initialize server thehulk.dmc.com. in a 192.1.1.1 -------------------------------------------------------------------------------- 2. I manually shutdown the name resolver and the domain server and deleted the cache file (*.mcom). 3. I rebooted the machine to get the communication system reset to a known clean spot. Interestingly enough, no combination of shutting down the name server, the name resolver, the ipacp or running domain/update seemed to get things into a known good state. It seemed to require a reboot. Now it seems to correctly resolve name requests although I'm still not able to get DOMAIN/LOOKUP to return anything sane (it always reports a server error). I'm going to declare victory, but I would like to point out that there are a couple of things that don't make sense. First, why should I have to tell the domain server how to contact the node upon which the domain server is started (that's what I believe the contents of the initialization file did). Second, if you MUST tell the domain server how to contact itself, why isn't that documented. Third, all of this is black magic and I just got it working by accident. There is no such thing as cause and effect. Anybody out there want to take a stab at an explanation? I would sure like to hear one. -- Dick Munroe Internet: munroe@dmc.com Doyle Munroe Consultants, Inc. UUCP: ...uunet!thehulk!munroe 267 Cox St. Office: (508) 568-1618 Hudson, Ma. FAX: (508) 562-1133