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

[Datastream #QOK-427508]: NPS: New "manager", Date problem

Hi,

re:
> I finally got the elastic IP to have the reverse lookup resolve
> to idd.foggy.nps.edu.  But I am getting access denied errors when
> executing the notifyme command:
> 
> nslookup idd.foggy.nps.edu
> Server:       172.20.20.11
> Address:      172.20.20.11#53
> 
> Non-authoritative answer:
> Name: idd.foggy.nps.edu
> Address: 35.167.101.77
> 
> ---------
> 
> dig -x 35.167.101.77
> 
> ; <<>> DiG 9.10.6 <<>> -x 35.167.101.77
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44887
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4000
> ;; QUESTION SECTION:
> ;77.101.167.35.in-addr.arpa.  IN      PTR
> 
> ;; ANSWER SECTION:
> 77.101.167.35.in-addr.arpa. 300       IN      PTR     idd.foggy.nps.edu.
> 
> ;; Query time: 10 msec
> ;; SERVER: 172.20.20.11#53(172.20.20.11)
> ;; WHEN: Mon Sep 23 22:02:28 PDT 2019
> ;; MSG SIZE  rcvd: 86
> --------------------

I see the same thing here using nslookup for both forward
and reverse DNS.

re:
> [ldm@idd logs]$ notifyme -vl- -f ANY -h idd.unidata.ucar.edu
> 20190924T050021.911175Z notifyme[4654]              notifyme.c:main:363       
>           NOTE  Starting Up: idd.unidata.ucar.edu: 20190924050021.911085 
> TS_ENDT {{ANY, ".*"}}
> 20190924T050021.911213Z notifyme[4654]              ldm5_clnt.c:forn5:460     
>           NOTE  LDM-5 desired product-class: 20190924050021.911085 TS_ENDT 
> {{ANY, ".*"}}
> 20190924T050021.911684Z notifyme[4654]              error.c:err_log:236       
>           INFO  Resolving idd.unidata.ucar.edu to 128.117.135.3 took 0.000423 
> seconds
> 20190924T050021.988917Z notifyme[4654]              
> ldm5_clnt.c:forn_signon:272         ERROR NOTIFYME(idd.unidata.ucar.edu): 7: 
> Access denied by remote server

I checked the LDM log files on each of the real-server backend
machines for the idd.unidata.ucar.edu cluster, and there are
only two machines that are being denied feed REQUESTs, and
neither of them has the name or IP address of your machine.
One of the machines is in AWS West 2, but its IP address is
54.68.55.178.

Questions:

- is it possible that the DNS is not active locally on
  your machine?

  One way to figure this out is to do a Google search
  using 'what is my ip' in a web browser run on your
  VM.  The other is to try and SSH to a machine under
  your control and look at the SSH logs to see where
  the attempt is coming from.

- when did you run your 'notifyme' test?

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: QOK-427508
Department: Support Datastream
Priority: Normal
Status: Open
===================
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.