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

[CONDUIT #FRD-124329]: CONDUIT feed request

Hi Elliott,

re:
> We would like to request access to the CONDUIT feed for four hosts.
> 
> 129.15.251.195
> 129.15.251.196
> 156.110.246.56
> 156.110.246.57
> 
> Please let us know what additional information is needed.

I verified that reverse DNS exists for the first two machines in your
list, so these machines can now REQUEST CONDUIT from idd.unidata.ucar.edu:

~: nslookup 129.15.251.195
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
195.251.15.129.in-addr.arpa     name = ingest0.irads.ou.edu.

Authoritative answers can be found from:
15.129.in-addr.arpa     nameserver = ooz.backbone.ou.edu.
15.129.in-addr.arpa     nameserver = zoo.backbone.ou.edu.

~: nslookup 129.15.251.196
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
196.251.15.129.in-addr.arpa     name = ingest1.irads.ou.edu.

Authoritative answers can be found from:
15.129.in-addr.arpa     nameserver = ooz.backbone.ou.edu.
15.129.in-addr.arpa     nameserver = zoo.backbone.ou.edu.

Reverse DNS does not, on the other hand, exist for the 3rd and 4th
machines in your list.  Since we prefer to _not_ add ALLOWs by IP
address, these machines are not ALLOWed to REQUEST CONDUIT from
idd.unidata.ucar.edu.

~: nslookup 156.110.246.56
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find 56.246.110.156.in-addr.arpa.: NXDOMAIN

~: nslookup 156.110.246.57
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find 57.246.110.156.in-addr.arpa.: NXDOMAIN

Please let us know when reverse DNS is setup for these machines and we
will add needed ALLOWs for them on idd.unidata.ucar.edu.

NB:

- most downstreams REQUESTing CONDUIT from top level IDD relays need to
  split their REQUEST line(s) into 5 or more mutually-exclusive REQUEST
  lines

  If you are not familiar with splitting feed REQUESTs, they look like the
  following:

Single REQUEST (not recommended):

request CONDUIT ".*" idd.unidata.ucar.edu

5 mutually exclusive REQUESTs:

REQUEST CONDUIT "([09]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([18]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([27]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([36]$)" idd.unidata.ucar.edu
REQUEST CONDUIT "([45]$)" idd.unidata.ucar.edu

Splitting a single feed REQUEST for a high-volume feed like CONDUIT
helps to minimize data receipt latencies.

re:
> Thanks

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: FRD-124329
Department: Support CONDUIT
Priority: Normal
Status: Closed