Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!sri-unix!teknowledge-vaxc!msimpson
From: msimpson@teknowledge-vaxc.ARPA (Mike Simpson)
Newsgroups: comp.bugs.4bsd
Subject: Re: Bus error in nslookup
Message-ID: <15707@teknowledge-vaxc.ARPA>
Date: Sun, 16-Aug-87 20:20:17 EDT
Article-I.D.: teknowle.15707
Posted: Sun Aug 16 20:20:17 1987
Date-Received: Mon, 17-Aug-87 00:43:34 EDT
References: <15704@teknowledge-vaxc.ARPA>
Reply-To: msimpson@teknowledge-vaxc.UUCP (Mike Simpson)
Organization: Teknowledge, Inc.; Los Angeles, CA
Lines: 16
Keywords: nslookup host server - causes bus error
Summary: second argument as host number works

In article <15704@teknowledge-vaxc.ARPA> mkhaw@teknowledge-vaxc.ARPA 
	(Michael Khaw) writes:
>I recently ftp'ed the latest 4.3 bind from ucbvax and installed it
>on my Ultrix 1.2 VAX.  "nslookup $host sri-nic.arpa" causes a "bus error"
>(but no core dump).  Nslookup works fine in interactive mode, and
>identifies sri-nic.arpa as the "root".  What's the fix, or where do I
>start looking?

	Making the second argument a host number (that is,
"nslookup sri-unix.arpa 10.0.0.9") seems to work all right.  (I found
this by accident.)
-- 
Mike Simpson		Teknowledge, Inc.  	Los Angeles, CA
Internet:msimpson@teknowledge-vaxc.arpa
Usenet: ...!{decvax,decwrl,harvard,seismo,sdcsvax,sri-unix,ucbvax,uw-beaver}!
		msimpson@teknowledge-vaxc.arpa