strange hostname....

[Pretender]

try resolving the hostname for 64.40.43.234

WTF? How is that even valid?

 

[Pretender]

C:\WINDOWS>tracert 64.40.43.234

Tracing route to PNAS [64.40.43.234]
over a maximum of 30 hops:




Uh?

 

[geno]

traceroute to 64.40.43.234 (64.40.43.234), 30 hops max, 40 byte packets
1 207.244.95.86 (207.244.95.86) 1.675 ms 1.379 ms 1.349 ms
2 Serial0-1-0.GW2.BOS1.ALTER.NET (157.130.3.141) 2.821 ms 2.135 ms 1.983 ms
3 153.ATM3-0.XR1.BOS1.ALTER.NET (152.63.25.170) 3.452 ms 2.305 ms 2.824 ms
4 191.at-1-0-0.TR1.NYC9.ALTER.NET (152.63.20.186) 9.242 ms 8.919 ms 8.686 ms
5 125.at-1-1-0.TR1.SEA1.ALTER.NET (146.188.140.90) 96.279 ms 96.468 ms 96.073 ms
6 199.ATM7-0.XR1.SEA1.ALTER.NET (146.188.200.101) 96.169 ms 96.539 ms 96.630 ms
7 195.ATM6-0.GW5.SEA1.ALTER.NET (146.188.201.65) 96.535 ms 96.348 ms 96.034 ms
8 ecco-gw.customer.alter.net (157.130.182.194) 95.183 ms 95.779 ms 94.462 ms

It dies there, but I can get a ping from it

 

[Yo Ma Ma]

Lookup and reverse lookup failed.



TraceRoute to 64.40.43.234 []

Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 209.237.131.3
2 0 0 16 157.130.73.121 serial4-1-1.gw1.orl1.alter.net
3 15 16 15 152.63.84.46 504.at-2-1-0.xr2.atl1.alter.net
4 16 31 16 152.63.10.77 0.so-3-0-0.tr2.atl1.alter.net
5 109 109 110 146.188.136.78 109.at-1-1-0.TR2.SEA1.ALTER.NET
6 109 94 109 146.188.200.113 198.atm6-0.xr2.sea1.alter.net
7 109 94 110 146.188.201.61 194.ATM4-0.GW5.SEA1.ALTER.NET
8 94 94 94 157.130.182.194 ecco-gw.customer.alter.net
9 109 109 110 64.40.40.1
10 94 94 109 64.40.40.15
11 359 344 344 64.40.43.234

Trace complete

No Domain Name Found

 

[amnesiac]

Wouldn't that mean it's probably someone's dialup connection?

 

[pulse8]

Even dialups generally have host names attached to them.

 

[Pretender]

ah I was getting something like this:



<< 5 113 ms 47 ms 42 ms gigaethernet5-0.core2.NewYork1.Level3.net [209.2
44.12.45]
6 40 ms 46 ms 40 ms so-4-1-0.mp2.NewYork1.level3.net [209.247.10.45]

7 48 ms 42 ms 48 ms so-3-0-0.mp1.Washington1.level3.net [209.247.8.4
1]
8 40 ms 39 ms 44 ms pos8-0.core2.Washington1.level3.net [209.247.10.
70]
9 54 ms 48 ms 47 ms ATM2-0.BR1.DCA6.ALTER.NET [204.255.168.193]
10 45 ms 55 ms 51 ms 0.so-3-0-0.XL1.DCA6.ALTER.NET [152.63.38.114]
11 45 ms 46 ms 45 ms 0.so-7-0-0.XR1.DCA6.ALTER.NET [152.63.38.86]
12 298 ms 91 ms 92 ms 0.so-4-0-0.TR1.DCA6.ALTER.NET [152.63.11.101]
13 676 ms 129 ms 128 ms 121.at-1-1-0.TR1.SEA1.ALTER.NET [146.188.140.74]

14 123 ms 128 ms 122 ms 199.ATM7-0.XR1.SEA1.ALTER.NET [146.188.200.101]

15 127 ms 127 ms 127 ms 195.ATM5-0.GW5.SEA1.ALTER.NET [146.188.201.57]
16 121 ms 126 ms 131 ms ecco-gw.customer.alter.net [157.130.182.194]
17 128 ms 126 ms 130 ms 64.40.40.1
18 127 ms 125 ms 122 ms 64.40.40.15
19 557 ms 372 ms 368 ms PNAS [64.40.43.234]
>>




i didn't think PNAS was a valid hostname, is it?

 

[Russ]

The IP belongs to nocharge.com. PNAS could be the name of the last router in the chain, or maybe even the system the user is on.

Russ, NCNE

 

[Mapidus]

<< C:\WINDOWS>tracert 64.40.43.234

Tracing route to PNAS [64.40.43.234]
over a maximum of 30 hops:
Uh? >>



I've seen those a lot. I don't know under what conditions this happens, but the PNAS is usually not the hostname, but comes from the users NetBios name under windows SMB protocol, the Microsoft Network Neighborhood name of the machine. I guess this name is registered when a proper hostname is not entered in windows.