At 02:18 PM 10/17/02 -0700, Mark Ivey wrote:
[...][...] You said the remote address was associated with dal.net. Do you have any references that explain how to track down where an address is? I never seem to be able to get that part. I would be happy to call it to their attention but I don't know where to send the e-mail.
You use the same tools to resolve addresses as you do FQNs -- host, nslookup, dig, and so forth (these are the common Linux/Unix applications, that is). They work only if the address has a reverse-lookup entry.
I rarely bother to complain about this sort of thing myself, but when I do, I address myself to postmaster@, abuse@, or the tech contact for the domain listed in its whois record. If none of these works, and the issue seems important enough, I use traceroute to figure out who the upstream ISP is and complain there.
My attempts to complain rarely seem to accomplish anything. I only suggested it here because tis seemed like an unusually focused acsn -AND- because dal.net had a good reputation back when I was familiar with it, so there's hope that they will see this as a problem to be addressed.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
