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

[LDM #BBH-396831]: nullproc_6 failure to rainbow.al.noaa.gov

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: [LDM #BBH-396831]: nullproc_6 failure to rainbow.al.noaa.gov
  • Date: Mon, 18 Jun 2012 10:08:06 -0600
Chris,

> Weather.mscd.edu has been unable to connect to rainbow.al.noaa.gov. I believe 
> this is due to our preparations for changing the domain name.  msudenver.edu 
> is now in our DNS and possibly breaking the reverse look-up.
> 
> $ nslookup 147.153.1.27
> Server:        75.75.75.75
> Address:    75.75.75.75#53
> 
> Non-authoritative answer:
> 27.1.153.147.in-addr.arpa    name = weather.msudenver.edu.
> 27.1.153.147.in-addr.arpa    name = weather.mscd.edu.
> 
> Please add  weather.msudenver.edu as an allowed host.

We can't add an ALLOW entry for "weather.msudenver.edu" to the LDM on 
"rainbow.al.noaa.gov" because we don't control that LDM. 
"weather.msudenver.edu" is, however, already allowed to connect to the LDM on 
"idd.unidata.ucar.edu" -- providing DNS resolution works correctly.

Do you want us to add an ALLOW entry for 21.1.153.147?

> Thanks,
> 
> Chris Kimmett
> 
> --
> Christopher Kimmett
> Unix Systems Administrator
> School of Letters, Arts, and Sciences
> Metropolitan State College of Denver
> address@hidden | 303.556.3932

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: BBH-396831
Department: Support IDD
Priority: Normal
Status: Closed