[3406] in Athena Bugs
nameserver deficiencies? (complaint from someone else)
daemon@ATHENA.MIT.EDU (John D. Kubiatowicz)
Thu Oct 12 17:17:49 1989
To: bugs@ATHENA.MIT.EDU
Date: Thu, 12 Oct 89 17:05:59 EDT
From: John D. Kubiatowicz <kubitron@ATHENA.MIT.EDU>
Check this out...
--KUBI--
------- Forwarded Message
Received: by E40-PO.MIT.EDU (5.45/4.7) id AA04179; Thu, 12 Oct 89 16:22:27 EDT
Received: from HARVARD.HARVARD.EDU by ATHENA.MIT.EDU with SMTP
id AA18454; Thu, 12 Oct 89 16:22:16 EDT
Message-Id: <8910122022.AA18454@ATHENA.MIT.EDU>
Received: by harvard.harvard.edu (5.54/a0.25)
(for kubitron@athena.mit.edu) id AA18805; Thu, 12 Oct 89 16:23:52 EDT
Received: from cfa201.HARVARD.EDU (cfa201.ARPA) by cfa; Thu, 12 Oct 89 16:22:43 edt
Date: Thu, 12 Oct 89 16:22:41 edt
Received: by cfa201.HARVARD.EDU; Thu, 12 Oct 89 16:21:34 EDT
From: thakur%cfa201@HARVARD.HARVARD.EDU (Manavendra K. Thakur)
To: kubitron@ATHENA.MIT.EDU
Subject: nameserver weirdness
Hi John,
How come the MIT nameservers don't know how to get nameservice
information for computers in Japan? Here's an example:
AlefNull% hostinfo 192.41.197.3
No such host.
AlefNull% hostinfo relay.cc.u-tokyo.ac.jp
No such host.
AlefNull% telnet 192.41.197.3
Trying...
Connected to 192.41.197.3.
Escape character is '^]'.
SunOS UNIX (relay.cc.u-tokyo.ac.jp)
login:
telnet> close
Connection closed.
AlefNull%
Here is a traceroute report:
AlefNull% traceroute 192.41.197.3
traceroute to 192.41.197.3 (192.41.197.3), 30 hops max, 40 byte packets
1 E40-03GW.MIT.EDU (18.72.0.1) 13 ms 13 ms 16 ms
2 W91GW.MIT.EDU (18.68.0.22) 366 ms 19 ms 17 ms
3 JVNCNET-GW1.MIT.EDU (18.92.0.12) 18 ms 15 ms 15 ms
4 BEANTOWN2-GATEWAY.JVNC.NET (130.94.27.9) 17 ms 21 ms 17 ms
5 CHEESESTEAK1-GATEWAY.JVNC.NET (130.94.27.249) 24 ms 21 ms 21 ms
6 CHEESESTEAK2-GATEWAY.JVNC.NET (130.94.32.2) 26 ms 25 ms 24 ms
7 CAPITAL1-GATEWAY.JVNC.NET (130.94.33.249) 27 ms 25 ms 28 ms
8 HOTBLACK-GATEWAY.JVNC.NET (130.94.1.10) 28 ms 31 ms 30 ms
9 FORD-GATEWAY.JVNC.NET (130.94.0.73) 32 ms 30 ms 34 ms
10 129.140.81.8 (129.140.81.8) 87 ms 78 ms 89 ms
11 129.140.79.17 (129.140.79.17) 149 ms 303 ms 163 ms
12 129.140.77.15 (129.140.77.15) 200 ms 226 ms 207 ms
13 129.140.13.130 (129.140.13.130) 227 ms 218 ms 215 ms
14 192.52.195.11 (192.52.195.11) 232 ms 274 ms 255 ms
15 132.160.249.1 (132.160.249.1) 310 ms 331 ms 342 ms
16 PACCOM.HAWAII.EDU (132.160.1.2) 359 ms 420 ms 335 ms
17 132.160.251.2 (132.160.251.2) 523 ms 535 ms 524 ms
18 133.4.1.1 (133.4.1.1) 527 ms 535 ms 548 ms
19 131.113.64.2 (131.113.64.2) 751 ms 546 ms 521 ms
20 192.41.197.3 (192.41.197.3) 614 ms 1675 ms 1010 ms
I can tell you that authoritative answers can be found for Japanese
hosts from the following machines:
RELAY.CC.U-TOKYO.AC.JP [192.41.197.3]
SH.CS.NET [192.31.103.3]
SH.CS.NET [128.89.0.92]
RELAY.CS.NET [192.31.103.4]
So why don't the MIT nameservers know this? I think you should yell
at somebody to do the right thing.
Manavendra
------- End of Forwarded Message
