MS>> This was only meant as an alternative to accomodate BBSers who must
MS>> connect using ~SSH~ then ~TelNet~ *SEPARATELY*, for some reason...

AB>> What reason?  Describe a scenario in which this makes sense.

 MS> Lets start with the BBS system from where i'm posting
 MS> right now.  I got "69.75.117.170" when i fed `NSLookUp'
 MS> with "BBSNets.COM" and then it led to two very distinct
 MS> results when i used `TraceRt'...  I have access to two
 MS> different ~ISP~s at home so i made this test with both
 MS> and here's what i found:  my 128 Kbps ~DSL~ feed gives
 MS> two consistent strings which show up as "bellnexia.net"
 MS> and "inet.qwest.net" in the listing;  with my DialUp
 MS> account there were three of these, somehwere in the
 MS> listing i got "sogetel.net", "vtl.net" and
"level3.net".
 MS> In both cases, it began with a Domain Name i could
 MS> associate with the ~ISP~ i used to ~TelNet~ and it ended
 MS> with what i believe to be the Domain Name of the ~ISP~
 MS> which gives access the remote BBS system.  Forget about
 MS> the exact ~IP~s and focus on paterns which can be
 MS> recognized time after time after time when the user
 MS> connects to the ~TelNettable~ BBS via his ~ISP~.

unreliable as rDNS (reverse dns) isn't required and is not set up by all
isps or even set up properly by all isps... decent idea, though... now,
IPv6 is a lot different and might fit something like this better...

)\/(ark