Umm... maybe these hosts don't need to be routed to at all. I would expect that any decent network would not waste global IP addresses on strictly local boxes.
If you look at their NS info you will see that three of the name servers listed are on private address space and are obviously internal name servers, forwarding all external queries to GATEKEEPER.cogentco.com. The only question at all is why these hosts are showing whois info. At worst it is a security leak-- and quite a bad one-- the opportunities for spoofing are enormous. Moreover, routers may have many interfaces and subinterfaces with different addresses (yes, some of them even *gasp* illegal rfc-1918 space).
The @Home network seems to like 10.0.0 space, do a traceroute to any host on it and more likely than not there will be a couple hops through "unroutable" space... ie probably internal ints on core routers. The only problem is if they bleed these routes externally.
Slashdot Mirror
Umm... maybe these hosts don't need to be routed to at all. I would expect that any decent network would not waste global IP addresses on strictly local boxes. If you look at their NS info you will see that three of the name servers listed are on private address space and are obviously internal name servers, forwarding all external queries to GATEKEEPER.cogentco.com. The only question at all is why these hosts are showing whois info. At worst it is a security leak-- and quite a bad one-- the opportunities for spoofing are enormous. Moreover, routers may have many interfaces and subinterfaces with different addresses (yes, some of them even *gasp* illegal rfc-1918 space). The @Home network seems to like 10.0.0 space, do a traceroute to any host on it and more likely than not there will be a couple hops through "unroutable" space... ie probably internal ints on core routers. The only problem is if they bleed these routes externally.