Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!van-bc!skl
From: skl@van-bc.wimsey.bc.ca (Samuel Lam)
Newsgroups: comp.unix.xenix.sco
Subject: Re: TCP/IP on XENIX 386 : SUMMARY
Message-ID: <41@van-bc.wimsey.bc.ca>
Date: 2 Nov 90 06:34:59 GMT
References: <6064@minyos.xx.rmit.oz> <NELSON.90Nov1002926@image.clarkson.edu>
Reply-To: skl@wimsey.bc.ca (Samuel Lam)
Organization: Balliffe Intersystem, Vancouver, B.C., Canada
Lines: 16

In article <NELSON.90Nov1002926@image.clarkson.edu>, nelson@clutx.clarkson.edu
 (Russ Nelson) wrote:
>According to my sources, SCO has acknowledged a bug in the name server
>resolution code that crashes the machine.  After I disabled the name server
>resolution, all the tcp-related crashes went away...

We were also having trouble with the SCO TCP/IP named.  I finally
ported Andy Poling's SysV port of BIND 4.7 to XENIX, and things
work much smoother after that.  (Still not quite perfect though...)

Someday I will either get the latest BIND ported or write "domaind",
(or "dnsd").

...Sam
-- 
Internet: <skl@wimsey.bc.ca>	UUCP: {van-bc,ubc-cs,uunet}!wimsey.bc.ca!skl