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

[LDM #EOT-784687]: LDM Access request

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 #EOT-784687]: LDM Access request
  • Date: Sat, 07 Nov 2020 09:14:59 -0700
Hi,

re:
> Yes, the first machine is still not working.

The public IP address of the machine REQUESTing a feed is sent to the
upstream machine which then attempts to determine the fully qualified
name of the machine.  When reverse DNS does not exist for the downstream
machine, the upstream LDM looks to see if there is an ALLOW that matches
the downstream machines IP.  Since we configuer our ALLOWs by fully
qualified machine name, not by IP address, a matching ALLOW will not
be found, and the REQUEST will be denied.  If your REQUEST is actually
making it to our relay cluster, it will not succeed if there is no
reverse DNS for your machine.  In this case, you should work with TAMU
network personnel to get reverse DNS properly setup for your machine.

re:
> The LDM docker on second
> machine has DNS error, which is unable to resolving the unidata DNS. I
> replaceed it to 8.8.8.8, and it is solved.

OK.  This situation is the opposite to the one that I describe above:
name resolution was not working on the second machine, and, by switching
to the Google DNS service, you solved that problem.

re:
> I will try to do the same thing on first machine to see if it works.

The 'nslookup' test that I reported on in my first reply showed that
DNS was not setup for your machine.  This is the thing that needs to
be addressed by someone at TAMU.

re:
> Thanks for your help.

No worries.

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: EOT-784687
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.