Hängt wohl ab vom zentralen rsyslog, und vom DNS bezüglich der reversen Auflösung.
Eine Schraube wäre wohl /etc/default/rsyslog:
# Options for rsyslogd
# -m 0 disables 'MARK' messages (deprecated, only used in compat mode < 3)
# -r enables logging from remote machines (deprecated, only used in compat mode < 3)
# -x disables DNS lookups on messages received with -r
# -c compatibility mode
# See rsyslogd(8) for more details
RSYSLOGD_OPTIONS="-c3"
Und noch diese, 'man rsyslogd':
-l hostlist
Specify a hostname that should be logged only with its simple hostname and not the fqdn. Multiple hosts may be specified using the colon (‘‘:’’) sepa‐
rator.
...
...
-q add hostname if DNS fails during ACL processing
During ACL processing, hostnames are resolved to IP addresses for performance reasons. If DNS fails during that process, the hostname is added as wild‐
card text, which results in proper, but somewhat slower operation once DNS is up again.
-Q do not resolve hostnames during ACL processing
Do not resolve hostnames to IP addresses during ACL processing.
-s domainlist
Specify a domainname that should be stripped off before logging. Multiple domains may be specified using the colon (‘‘:’’) separator. Please be
advised that no sub-domains may be specified but only entire domains. For example if -s north.de is specified and the host logging resolves to
satu.infodrom.north.de no domain would be cut, you will have to specify two domains like: -s north.de:infodrom.north.de.
Oct 16 23:41:20 ck-a800-xeny.local kkadmin: x
rsyslog hat erkannt, daß es die eigene Maschine ist, und gar nicht den DNS befragt?
------------------
Nette Option, falls nur rsyslog verwendet wird:
RELP ( imrelp, omrelp ) statt TCP oder UDP
(leider erst ab squeeze)