In message <[email protected]> Michael Richardson writes: > >>>>> "Curtis" =3D=3D Curtis Villamizar <[email protected]> writes: > Curtis> Every log file that tries to record host names becomes much more > Curtis> readable if it is successful in recording host names than if it > Curtis> records IP addresses. In some cases for performance reasons the > log > Curtis> files have to record IP addresses, but that would not be expected > to > Curtis> be the case for home use. It is even worse if the log files > record IP > Curtis> addresses and the person reading the logs has no reverse > Curtis> map. > > the machines recording the addresses/names are not in the home. > They are the web servers that the home user talks to.
Yes. I know that. Or a mail server, etc none of which is not in the home. If a problem is reported to the home user, then having a mapping of address in the logs to host name would be a real good idea. http logs on heavily loaded servers always record just the IP address because the overhead of the rDNS lookups is too high. I mentioned that in prior email. Very rarely is an end customer ever contacted, except perhaps an automated mail from postmaster on an email server or a rare note from a provider saying their host is compromised and is attacking others. > Michael Richardson <[email protected]>, Sandelman Software Works=20 > IETF ROLL WG co-chair. http://datatracker.ietf.org/wg/roll/charter/ Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
