Article View: comp.sys.sun
Article #1415Re: rpc.bootparamd uses nameserver: single point failure?
From: Jon A. Tankersley
Date: Sat, 02 Sep 1989 04:53
Date: Sat, 02 Sep 1989 04:53
10 lines
937 bytes
937 bytes
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-
Technical Details
Message-ID:
<1469@brazos.Rice.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!att!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-requestShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!watmath!att!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request From: tank@apctrc.trc.amoco.com (Jon A. Tankersley) Newsgroups: comp.sys.sun Subject: Re: rpc.bootparamd uses nameserver: single point failure? Keywords: Networks Message-ID: <1469@brazos.Rice.edu> Date: 2 Sep 89 04:53:45 GMT Sender: root@rice.edu Organization: Sun-Spots Lines: 10 Approved: Sun-Spots@rice.edu X-Sun-Spots-Digest: Volume 8, Issue 121, message 5 of 17