On 9/1/97 12:48 AM, Doppleganger Software (doppsoft@JUNCTIONNET.COM)
stated:
>Well, unless I am mistaken, the reason for this is that the MUD is trying
>to resolve the hostname. And since there is no IP of that number, it
>can't get a host name, and as such, has to time out. There are a few
>things you can do if that is the problem. #1., get the asyncrynous name
>resolver from the site. or #2. Turn slow NS on, then it won't resolve
>the hostnames. Maybe you can even try and use it to track them down.
>Good luck, those sick people (probably friends with those sending junk
>e-mails) should be dragged out into the street and shot.
No, I've had regular non-domain name IPs work, even with slowns it is
slow as shizzit.
The IP doesn't exist at all, not even pingable... I mean, 002.000.000.000
and 000.000.000.000 don't really exist...
- Chris Jacobson
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST