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 Tony, re: > Since the previous email was received, our server has been moved to > another location. The IP address may have changed (131.247.242.26), > though I don't remember what it was before, but the name remains the > same (unidata.rc.usf.edu). I am sending this email, because the machine > is no longer able to access the datastream servers. See below. > I pasted the output > of the "notifyme" utility below. I am hoping that it is just a matter > of updating the access list for those machines. If you need anymore > information, please let me know. > > notifyme -vl- -h idd.cise-nsf.gov > Jan 30 19:20:06 notifyme[18789] NOTE: Starting Up: idd.cise-nsf.gov: > 20120130192006.341 TS_ENDT {{ANY, ".*"}} > Jan 30 19:20:06 notifyme[18789] NOTE: LDM-5 desired product-class: > 20120130192006.341 TS_ENDT {{ANY, ".*"}} > Jan 30 19:20:06 notifyme[18789] INFO: Resolving idd.cise-nsf.gov to > 192.12.209.62 took 0.023776 seconds > Jan 30 19:20:06 notifyme[18789] ERROR: NOTIFYME(idd.cise-nsf.gov): 7: > Access denied by remote server > > notifyme -vl- -h idd.unidata.ucar.edu > Jan 30 19:21:48 notifyme[18796] NOTE: Starting Up: idd.unidata.ucar.edu: > 20120130192148.775 TS_ENDT {{ANY, ".*"}} > Jan 30 19:21:48 notifyme[18796] NOTE: LDM-5 desired product-class: > 20120130192148.775 TS_ENDT {{ANY, ".*"}} > Jan 30 19:21:48 notifyme[18796] INFO: Resolving idd.unidata.ucar.edu to > 128.117.140.3 took 0.02279 seconds > Jan 30 19:21:48 notifyme[18796] ERROR: NOTIFYME(idd.unidata.ucar.edu): > 7: Access denied by remote server The reason for the denial is the lack of _both_ forward and reverse DNS for your machine. The following 'nslookup' invocations demonstrate the lack of DNS: Name to IP works: % nslookup unidata.rc.usf.edu Server: 192.168.72.2 Address: 192.168.72.2#53 Non-authoritative answer: Name: unidata.rc.usf.edu Address: 131.247.242.26 IP to name does NOT work: % nslookup 131.247.242.26 Server: 192.168.72.2 Address: 192.168.72.2#53 ** server can't find 26.242.247.131.in-addr.arpa.: NXDOMAIN It is the IP to name DNS that is needed by the LDM since the IP address of the machine requesting data is included in the data REQUEST, and the LDM on the upstream machine needs to be able to translate that IP into a fully-qualified hostname which can be checked against ~ldm/etc/ldmd.conf ALLOW rules. As soon as both forward and reverse DNS is available for your machine, the 'notifyme' invocations below will work. Please contact your networking folks to get the DNS issue resolved. 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: SVQ-893979 Department: Support IDD Priority: Normal Status: Closed