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

[LDM #GHA-946718]: Lost connectivity to idd.unidata.ucar.edu at 10:41 UTC


> Are supposed to be resolving to for idd.unidata.ucar.edu?

No.  We moved the IP address from the old cluster (the on in the NWSC
computer room) to the new cluster (the one in the NCAR Mesa Lab), so
the IP address was and continues to be: is the IP address for the old cluster.  Until the cluster
was turned off (mostly last night), one could REQUEST feed(s) from it,
but I noted that you were _not_ REQUESTing from it.

> ldm@mammatus:~$ ldmping idd.unidata.ucar.edu
> 20210726T145704.284118Z ldmping[13391] INFO ldmping.c:51:print_label()      
> State    Elapsed Port   Remote_Host           rpc_stat
> 20210726T145704.284384Z ldmping[13391] INFO error.c:236:err_log() Resolving 
> idd.unidata.ucar.edu to took 0.000187 seconds
> root@mammatus:~# nslookup idd.unidata.ucar.edu
> Server:
> Address:
> Non-authoritative answer:
> Name:   idd.unidata.ucar.edu
> Address:

This is the correct IP address.

> I'm getting different DNS resolutions between linux nslookup and ldmping.

That is very interesting indeed.  Did someone hardwire an IP <-> name
association in the /etc/hosts file on mammatus?


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: GHA-946718
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.