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.
I am starting to think that you are doing it on purpose, but of course I am wrong, there is no reason why you would keep removing my machine from your ldmd.conf file, right? Could you please add again ebb.stanford.edu to your feeding line? Naturally, if this happens again, I will report this problem directly to unidata.
I've got you in my ldmd.conf file as both ebb.stanford.edu and the IP address 171.64.54.5 (which is what my DNS says ebb.stanford.edu should link to). I'm not sure what else I can do.
When I restart my ldm and do a ldmadmin tail, I immediately get messages that two unknown IP's (134.129.217.28 and 134.197.100.156) are attempting to make connection, but are being refused. When I do nslookup on those IP's, the DNS can't find them.
So, if those are your's, then either my DNS is not updating properly or your systems administrator is doing you a disservice. Beyond that, let's do throw this problem into the UPC's lap.
How about it, Unidata, got any ideas? Larry ---===---=-=-=-=-=-=-=-=-=-=-=====[\/]=====-=-=-=-=-=-=-=-=-=-=---===--------===(* Climate's what we expect, but weather's what we get. *)===----- Larry Riddle : Climate Research Division : Scripps Institution of Oceanography
University of California, San Diego : La Jolla, California 92093-0224 Phone: (858) 534-1869 : Fax: (858) 534-8561 : E-Mail: address@hidden