Name Server Problems
carlfoss at world.std.com
carlfoss at world.std.com
Tue Jan 4 17:24:59 UTC 2000
Does anyone out there know what may be going on here? I have another
server that connects perfectly well, but this one does not. I tried
identifying two name servers in db.zoneinfo (this server is a windows NT
machine) rather than the one, because this was trying to use 209.61.89.145
as the name server, and the working one was identifying 199.0.65.2 as the
only name server when I did an nslookup. The gambit of adding the second
explicit name server seems to have worked, in that I get responses now to
nslookup, but it remains that 209.... is apparently not functioning as a
name server, or at least is not recognized. Here is the information from
some of the diagnostics.
The problem now appears to be that 209.61.89.145 is for some reason not
recognizable as a server/host/...
[nslookup at command prompt
First response is that cannot find server name for 209.61.89.145 Non
existent host/domain.]
Default Server: zork.tiac.net
Address: 199.0.65.2
> > ls
Server: zork.tiac.net
Address: 199.0.65.2
[This is recognized as a name server and was specified as such in
db.zoneinfo.]
Name: ls
> set all
Default Server: zork.tiac.net
Address: 199.0.65.2
Set options:
nodebug defname search recurse
nod2 novc noignoretc port=53
querytype=A class=IN timeout=5 retry=4
root=a.root-servers.net.
domain=
srchlist=
>
Here are the traceroutes, one from this machine to the outside world, and
the other an attempt to go in to the machine from the outside. Note that I
can go out but not in.
world% traceroute 199.0.65.2 (to the gateway for my server where it
connects to the ISP)
traceroute to 199.0.65.2 (199.0.65.2), 30 hops max, 40 byte packets
1 Boston-STD-F.std.com (199.172.62.80) 2 ms 2 ms 2 ms
2 Loopback0.GW5.BOS1.ALTER.NET (137.39.4.111) 5 ms 4 ms 7 ms
3 153.ATM2-0.XR1.BOS1.ALTER.NET (146.188.179.250) 3 ms 8 ms 3 ms
4 291.ATM3-0.XR1.EWR1.ALTER.NET (146.188.176.141) 9 ms 8 ms 9 ms
5 193.ATM1-0-0.BR1.EWR1.ALTER.NET (146.188.176.49) 8 ms 9 ms 10 ms
6 204.6.117.5 (204.6.117.5) 84 ms 65 ms 200 ms
7 38.1.10.254 (38.1.10.254) 48 ms (ttl=247!) 52 ms (ttl=247!) 51 ms
(ttl=24
7!)
8 204.6.140.54 (204.6.140.54) 28 ms (ttl=246!) 34 ms (ttl=246!) 36 ms
(ttl=
246!)
9 zork.tiac.net (199.0.65.2) 76 ms (ttl=54!) 81 ms (ttl=54!) 78 ms
(ttl=54!
)_________________________
world% traceroute 209.61.89.145 (to the server itself)
traceroute to 209.61.89.145 (209.61.89.145), 30 hops max, 40 byte packets
1 Boston-STD-F.std.com (199.172.62.80) 2 ms 2 ms 3 ms
2 Loopback0.GW5.BOS1.ALTER.NET (137.39.4.111) 9 ms 3 ms 4 ms
3 153.ATM2-0.XR2.BOS1.ALTER.NET (146.188.179.254) 4 ms 10 ms 3 ms
4 290.ATM3-0.XR2.EWR1.ALTER.NET (146.188.176.157) 16 ms 8 ms 9 ms
5 192.ATM11-0-0.BR1.EWR1.ALTER.NET (146.188.176.61) 8 ms 8 ms 8 ms
6 204.6.117.5 (204.6.117.5) 17 ms 19 ms 11 ms
7 38.1.10.254 (38.1.10.254) 41 ms (ttl=247!) 29 ms (ttl=247!) 27 ms
(ttl=24
7!)
8 204.6.140.54 (204.6.140.54) 36 ms (ttl=246!) 30 ms (ttl=246!) 28 ms
(ttl=
246!)
9 38.16.82.113 (38.16.82.113) 41 ms (ttl=53!) 37 ms (ttl=53!) 30 ms
(ttl=53
!)
__________________________
Tracing route to world.std.com [192.74.137.5] (to the outside world)
over a maximum of 30 hops:
1 201 ms 200 ms 180 ms 38.16.84.113
2 301 ms 280 ms 281 ms bedford.ma.tiac.ne.us.psi.net [38.16.82.1]
3 321 ms 280 ms 280 ms rc6.ne.us.psi.net [38.1.41.6]
4 281 ms 280 ms 281 ms rc1.ne.us.psi.net [38.1.21.97]
5 281 ms 220 ms 200 ms 38.1.3.41
6 201 ms 200 ms 200 ms 204.6.140.118
7 221 ms 200 ms 200 ms 159.ATM2-0.XR2.DCA8.ALTER.NET [152.63.35.202]
8 220 ms 220 ms 241 ms 188.ATM2-0.TR2.DCA8.ALTER.NET
[146.188.163.82]
9 201 ms 220 ms 200 ms 115.ATM7-0.TR2.NYC1.ALTER.NET
[146.188.138.170]
10 340 ms 221 ms 220 ms 198.ATM6-0.XR2.BOS1.ALTER.NET
[146.188.179.97]
11 * 241 ms 200 ms 190.ATM8-0-0.GW5.BOS1.ALTER.NET
[146.188.179.245]
12 200 ms 220 ms 200 ms Boston-STD.std.com [192.74.137.80]
13 361 ms * 281 ms world.std.com [192.74.137.5]
Trace complete.
________________________
More information about the bind-users
mailing list