🚀 go-pugleaf

In article <159j2mINNh3n@network.ucsd.edu> sfl@muttley.ucsd.edu (Susan  
Fichera) writes:
> Has someone solved the following problem simply?  I have NeXTs behind a
> Sun gateway. I have a resolv.conf file that lists various alternative
> nameservers, the gateway being at the top of the list.  If the gateway
> goes down and then comes back up, the NeXTs are left in a state where
> they can not resolve any host names that are not explicitly listed in
> /etc/hosts. They do not refer to the gateway nameserver or any of the
> other nameservers listed in resolv.conf. The solution has been to
> reboot the NeXTs after the gateway comes back on the net. I'm looking
> for a better way. 

A known bug in both SunOS 4.1.2 and NeXT OS 2.x.  Hopefully fixed in 3.0  
???
Only the first nameserver is actually consulted.  You 'shouldn't' have to  
reboot the client NeXTs, but they won't be able to resolve names until the  
Sun comes back up.  Does anyone have a fix for this? 
--
David Lemson                                           (312) 732-4741
FNBC Sys Admin (Summer) UIUC NeXT Campus Consultant(rest of the time)
E-mail to: lemson@fnbc.com                          NeXTMail accepted