Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!ENG.SUN.COM!cpj
From: cpj@ENG.SUN.COM (Chuck Jerian)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Domain Name Screaming
Message-ID: <8907021941.AA18820@sparky.Eng.Sun.COM>
Date: 2 Jul 89 19:41:18 GMT
References: <37397@sgi.SGI.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Sun Microsystems, Mountain View
Lines: 19

I've made about the same changes to a version of yp but never
put them into a release, and have a newer version that does positive
and negative caching, and never forks, its based on a new
asynchronous resolver interface. 
What it does is record that a request is outstanding
and start up the asynchronous resolver,
this is recorded, and any further yp requests for this question
are dropped until the asynchronous resolver succeeds or fails,
the success or failure is cached and used to answer subsequent
requests for some lifetime.
I've also overloaded the  no_more_keys response to be soft error,
for hosts by name, and have arranged for multiple ip addreses 
to be returned by  returning a yp response of the form:

"bogus.com  1.2.3.4\nbogus.com 1.5.4.1"

I've also changed rpc to use exponential backoff at all times,
this eliminates the close spacing of the rpc requests.
			--cpj