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.
Hi Brian, Sorry for the slow reply... we are right in the middle of hosting training workshops this week (and half of next week), and it has been hard to attend to pending support issues. re: > Unfortunately the machine can't be made available to public DNS's. It is > only registered with our internal DNS. This is unfortunate. re: > [ldm@ldm2 ~]$ nslookup ldm.oce.usda.gov > Server: 199.128.189.124 > Address: 199.128.189.124#53 > > Name: ldm.oce.usda.gov > Address: 199.128.189.9 > > I believe the machine was hardwired for ALLOW on the previous setup. I > have control over the firewall but suspect that wouldn't help in making > the machine more visible. No it wouldn't. Reverse DNS (IP->fully qualified name) is the setup that makes thing much easier and less brittle. re: > Can you hardwire even if it is undesirable or advise on another solution? We can hardware something (or work with another high level relay site to do the same), but we won't be able to attend to it today); sorry. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: TSO-178323 Department: Support IDD Priority: Normal Status: Open