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.
Jeff, Never mind, that was a red herring. All the configs here use the idd.wunderground.com hostname. I'll keep thinking on it. We're also working on the rtstats traceroute issue which seems to be a stateful packet filtering issue. mike On May 19, 6:43pm, Jeff Masters wrote: > Subject: Re: 20050512: Routing from winderground to idd and rtstats > > Hi Mike, the machine also has the name idd.wunderground.com, which is > connected to an IP number. Would making that name in your allow fix > things? The machine knows itself as n8.wunderground.com, which as you > said, is an internal IP only. > > Jeff > > On Thu, 19 May 2005, Mike Schmidt wrote: > > > Jeff, > > > > On May 19, 2:19pm, Jeff Masters wrote: > > > Subject: Re: 20050512: Routing from wunderground to idd and rtstats > > > > > > Hi Mike, I am running ldm 6.2.1, do I need to upgrade? > > > > There's no compelling reason to that with regard to these concerns. > > > > > the ldmd.log file for the machine n8.wunderground.com is available via: > > > > > > ftp ftp.wunderground.com > > > Name (ftp.wunderground.com:root): ftp > > > 331 Anonymous login ok, send your complete email address as your password. > > > Password: > > > ftp> cd auto > > > ftp> get ldmd.log > > > > Thanks > > > > > You won't be able to get a directory listing for security reasons, you > > > have to know the file name and dir. > > > > > > It's curious about the "No route to host" thing, I just did some > > > traceroutes, and one to rtstats.unidata.ucar.edu failed at the last hop > > > (flrb.ucar.edu), but succeeded to idd.unidata.ucar.edu. I was able to ping > > > both machines. > > > > > > Thanks, Jeff > > > > >From our end, I now see the same problem. It looks like all the > > authoratative name servers for wunderground.com are giving out a > > private address for n8.wunderground.com (ie 10.0.10.91)? > > > > mike > > >-- End of excerpt from Jeff Masters