On Fri, 14 Mar 2014, Tanky Woo wrote:
If the timeout is because the name really doesn't exist in DNS and you get
a timeout rather than a 'does not exist' message, a cacheing server won't
help.
but then the system config is wrong in the first place... Why use a name
that cannot be resolved?
Rainer
Because the network environment is special, I have describe the env in the mail:
http://lists.adiscon.net/pipermail/rsyslog/2014-March/036856.html
I'm confused now. Is your problem that you are receiving messages and running
into problems resolving IPs as you are receiving messages?
or that you are trying to send messages to a name that doesn't exist.
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
