Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!crdgw1!uunet!mcsun!tuvie!chytil
From: chytil@tuvie (Inst.f.Techn.Informatik)
Newsgroups: comp.sys.apollo
Subject: experiencing named-timeouts : hints ?
Message-ID: <1947@tuvie>
Date: 1 Nov 90 20:17:46 GMT
Reply-To: chytil@vlsivie.tuwien.ac.at (Georg Chytil)
Organization: Vienna University of Technology, Dept. of VLSI-Design
Lines: 35

We are running the bsd-named supplied with 10.2 on our gateway-node (DN3500)
and on a DN3010, both as secondary servers, since the administration of our
subdomain is done by our 'parent'-domain ( long live bureaucracy I. !!! ).

After experiencing irregular host-resolution-failures ( ~ every 15 minutes for
some minutes ) I queried our named's with help of nslookup (not supplied with
Domain/OS) from an Ultrix-host, and came up with something like ( set debug ).

Got answer : Type is A			(actually longer ..)
timeout1
timeout2
timeout3
timeout4

While I'm not a great binder I assume that a successful resolution consists of
at least _two_ packets from the server, and that the Apollo-named sometimes 
messes up with the second one .....
the named.run-logfile showed the query, but nothing unusual ...

Two questions :

	o has anybody else experienced such failures and can provide me with
		some enlightment concerning my idle 2-packets-speculation ?

	o is there a remedy -- or am I just plain wrong ?



								Georg
 
-- 
<------------Golden apples of the sun, silver apples of the moon-------------->
Chytil Georg Systemdamager@Dep. of VLSI (vlsivie)   TU Wien A-1040 Wien Austria
chytil@vlsivie.{tuwien.ac.at,uucp}  chytil@egh780.una.at  +43/(0)222/58801/8146
#include <extra_disclaimer.h>         Don't panic!       Fax: +43/(0)222/569697