[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DNS operational (fwd)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: DNS operational (fwd)
  • Date: Fri, 4 Aug 2000 11:16:36 -0600 (MDT)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Fri, 4 Aug 2000 10:05:06 -0600 (MDT)
From: Greg Woods <address@hidden>
To: address@hidden, address@hidden
Subject: DNS operational

All DNS service has been fully restored. Turns out that named dumping
core yesterday filled up the /local filesystem on fl-phx which caused
additional complications.

named monitoring scripts should be installed on fl-phx and bubby this morning.
This won't necessarily prevent a crash like yesterday's, but it would cause
it to be detected and restarted much sooner.

Just to clarify one thing: the IP address 128.117.98.83 corresponds to an
old machine named tijeras which has been dead for FOUR YEARS now. Please
remove all references to this IP address from your DNS configurations.

Please note that the recommended DNS configuration for the various types
of hosts can be found on the web at:

http://www.scd.ucar.edu/hps/dns.html

--Greg