rpc.bootparamd uses nameserver: single point failure?
Jon A. Tankersley
tank at apctrc.trc.amoco.com
Sat Sep 2 14:53:45 AEST 1989
I'd set up my own nameservers for my local network and let bootparamd use
them when booting. What I have in place is ypserv/named. I keep the
local network info in the local yp and named resolves everything else.
This works fine with redundant nameservers - you're supposed to have two
anyway, but loss of the primary in a catastrophic fashion (unplug, crash,
etc.) will hang telnet,rlogin, etc.
4.1 is supposed to fix this.
-tank-
More information about the Comp.sys.sun
mailing list