Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!rice!sun-spots-request
From: aklietz@occam.ncsa.uiuc.edu (Alan Klietz)
Newsgroups: comp.sys.sun
Subject: Re: YP: binding client to server not on same broadcast net
Keywords: Networks
Message-ID: <4922@brazos.Rice.edu>
Date: 11 Feb 90 18:02:30 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 17
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n6, Replies: v9n19
X-Sun-Spots-Digest: Volume 9, Issue 33, message 7

In article <4557@brazos.Rice.edu> David.Maynard@K.GP.CS.CMU.EDU writes:
[about how to bind a client to a YP server on a remote subnet.]

I modified ypbind to consult a file containing a list of potential YP
servers in a manner similar to the /etc/resolv.conf file that BIND uses.
My /etc/ypserv.conf file looks like this,

domain ncsa
ypserver 128.174.23.1
ypserver 128.174.20.10

Each potential ypserver is polled.  If none is found, the first candidate
is polled again and so on round-robin.  A backoff algorithm is used to
reduce the number of polls after a given amount of time.  Works great.

Alan E. Klietz
Internet:  aklietz@ncsa.uiuc.edu