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

[LDM #NAJ-908127]: feed

Hi Erik,

re:
> Hi there - we were able to get the forward and reverse entries for our
> servers registered, but from my end I still see connection errors in the
> logs.
> 
> Are you able to do forward and reverse lookups of verify1.crh.noaa.gov and
> verify2.crh.noaa.gov on your end?

I just verified reverse DNS (IP -> name) for both of your machines.

If you are still getting connection denied messages in your LDM log file,
there is something else wrong.

As a sanity test, can you please send us the output from the following:

<as 'ldm' on verify1>

notifyme -vl- -f ANY -h idd.unidata.ucar.edu

Thanks in advance...

> Thanks,
> Erik
> 
> address@hidden> wrote:
> 
> > Hi Erik,
> >
> > Steve is out of the office today, so I'll answer in his stead...
> >
> > re:
> > > We published verify1.crh.noaa.gov and verify2.crh.noaa.gov to external
> > dns,
> > > so they should be resolvable now.
> > >
> > > I'm still seeing the connection being refused on our end, is there a DNS
> > > refresh you need to do on your end?
> >
> > The problem is that reverse DNS (IP -> name) has not been setup for
> > these machines.  For instance:
> >
> > % nslookup verify1.crh.noaa.gov
> > Server:         128.117.64.44
> > Address:        128.117.64.44#53
> >
> > Non-authoritative answer:
> > Name:   verify1.crh.noaa.gov
> > Address: 204.227.126.162
> >
> > % nslookup 204.227.126.162
> > Server:         128.117.64.44
> > Address:        128.117.64.44#53
> >
> > ** server can't find 162.126.227.204.in-addr.arpa.: NXDOMAIN
> >
> > % nslookup verify2.crh.noaa.gov
> > Server:         128.117.64.44
> > Address:        128.117.64.44#53
> >
> > Non-authoritative answer:
> > Name:   verify2.crh.noaa.gov
> > Address: 204.227.126.163
> >
> > % nslookup 204.227.126.163
> > Server:         128.117.64.44
> > Address:        128.117.64.44#53
> >
> > ** server can't find 163.126.227.204.in-addr.arpa.: NXDOMAIN
> >
> > Reverse DNS is needed to resolve the IP address into a fully
> > qualified name since it is the IP address that is sent by the
> > downstream LDM to the upstream LDM.
> >
> > As soon as reverse DNS is setup for the machines AND the names
> > that are resolved end in '.gov', your feed REQUEST(s) will work
> >
> > 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: NAJ-908127
> > Department: Support LDM
> > 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.
> >
> >
> >
> 
> 

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: NAJ-908127
Department: Support LDM
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.