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 Scott, re: > I apologize if you're already working on this. I saw this case about > the UNIWISC data, but I wasn't sure it applied to the CONDUIT data too. Probably not since the UNIWISC feed problem was isolated to idd.ssec.wisc.edu and for one particular user. re: > I haven't received any gfs or nam data from idd.unidata.ucar.edu since > yesterday. Should this be a separate case, or am I being impacted by > this same problem? Questions: - what messages related to the CONDUIT feed REQUEST(s) are you seeing in your LDM log file? - what are the fully qualified name and IP address of your machine that is trying to get CONDUIT data from idd.unidata.ucar.edu? Comment: It is possible that reverse DNS (IP -> name) does not exist for your machine, so the ALLOW(s) that would grant your feed REQUEST(s) are being denied by idd.unidata.ucar.edu. If this is the case, the fix is for reverse DNS to be (re)established for your machine. 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: WJF-152207 Department: Support CONDUIT Priority: Normal Status: Closed