failure of host name resolution

Article View: comp.sys.next.sysadmin

Article #314

Back to comp.sys.next.sysadmin Previous Next

#314

From: Susan Fichera
Date: Thu, 30 Jul 1992 20:22

15 lines
1099 bytes

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.  


Thanks for any suggestions.

Susan Fichera
sfl@grasshopper.ucsd.edu

Technical Details

Message-ID: <159j2mINNh3n@network.ucsd.edu>

Path:

arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!network.ucsd.edu!muttley!sfl

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!network.ucsd.edu!muttley!sfl
From: sfl@muttley.ucsd.edu (Susan Fichera)
Newsgroups: comp.sys.next.sysadmin
Subject: failure of host name resolution
Message-ID: <159j2mINNh3n@network.ucsd.edu>
Date: 30 Jul 92 20:22:46 GMT
Distribution: usa
Organization: Department of Music, UC San Diego
Lines: 15
NNTP-Posting-Host: muttley.ucsd.edu