20040820: nullproc_6 errors from atm.geo.nsf.gov

>From: David Fitzgerald <address@hidden>
>Organization: Millersville University of Pennsylvania
>Keywords: 200408141648.i6MGmfaW028555 IDD DNS

Hi Dave,

>Following up on the DNS errors between atm.geo.nsf.gov and twister, I just
>restarted the ldm on twister today and once again I am seeing nullproc_6
>errors, and I'm sure atm is getting errors in its log file.  If I let my ldm
>go, it will eventually connect to atm, but not after an hour or so.  This
>has to be some DNS or routing problem between MU and nsf.gov.  Could you
>send me the DNS server(s) that atm uses

'atm' is setup with its own caching name server:

% nslookup twister.millersville.edu
Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   twister.millersville.edu
Address: 166.66.44.84

>and a traceroute from atm to twister?

Here it is:

% traceroute twister.millersville.edu
traceroute to twister.millersville.edu (166.66.44.84), 30 hops max, 40 byte 
packets
 1  colima.nsf.gov (198.181.231.1)  7 ms  1 ms  1 ms
 2  arlg-nsf.maxgigapop.net (206.196.177.137)  2 ms  3 ms  1 ms
 3  dcne-so3-0-0.maxgigapop.net (206.196.178.42)  1 ms  2 ms  5 ms
 4  abilene-rtr.maxgigapop.net (206.196.177.2)  4 ms  20 ms  16 ms
 5  204.238.76.1 (204.238.76.1)  24 ms  6 ms  4 ms
 6  204.238.76.14 (204.238.76.14)  6 ms  6 ms  6 ms
 7  172.16.166.1 (172.16.166.1)  11 ms  124 ms *
 8  192.206.29.254 (192.206.29.254)  50 ms  35 ms  37 ms
 9  166.66.251.17 (166.66.251.17)  36 ms  12 ms  12 ms
10  166.66.44.84 (166.66.44.84)  12 ms  12 ms  12 ms

>Our networking guys want this data to troubleshoot the problem.

I'll be interested in what they have to say.

>Thanks!!

No worries.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.