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

[LDM #HXD-230534]: ldm DNS reverse resolution question

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 #HXD-230534]: ldm DNS reverse resolution question
  • Date: Thu, 05 Mar 2009 16:18:10 -0700
Mike,

> I found this comment written by Anne Wilson in the ldm support email
> archive for 2001:
> 
> The LDM requires that both that the name resolves to the IP address
> *and* the IP address resolves to the name.

To the best of my knowledge, it's not true that forward and reverse
DNS lookups must agree in order for the LDM to work.  As the LDM
developer, I'd hope I'd know.  Of course, I could be getting senile.  :-)

> We are considering configuring our new ldm server in such a way that
> it might work like this:
> 
> We issue a request from dmadisi.esrl.noaa.gov, but the reverse lookup
> on that IP would return something like dmadisi.boulder.noaa.gov.
> I have two questions:
> 
> 1) Does the 2001 comment above mean this is a showstopper when we
> make connections to request data from other ldm servers?
> 
> 2) Would this have any impact on users who initiated the connections
> to dmadisi?

You should be fine.

> Thanks,
> 
> Mike

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: HXD-230534
Department: Support LDM
Priority: Normal
Status: Closed