Thank you David! The omfwd action parameter RebindInterval (a.k.a.
$ActionSendTCPRebindInterval or $ActionSendUDPRebindInterval in the old
texts) is exactly what is needed (and really the best that could be
expected for UDP). I have a TCP use for it in our environment as well.
Learn something new every day.
Regards,
**
On 5/30/20 7:51 PM, David Lang via rsyslog wrote:
you _really_ don't want rsyslog to do a DNS lookup for every packet,
it would crush your DNS server and everything would slow to a crawl.
look at rebind interval, that will have rsyslog redo the connection
every X messages/batches to support load balancing.
David Lang
On Sun, 31 May 2020, Olivia Nelson via rsyslog wrote:
Date: Sun, 31 May 2020 08:42:30 +0800
From: Olivia Nelson via rsyslog <[email protected]>
To: rsyslog-users <[email protected]>
Cc: Olivia Nelson <[email protected]>
Subject: Re: [rsyslog] rsyslog does not forward logs to new IP address,
when DNS A record is updated
David,
We have a large network, 700K hosts in total, 30+ facilities, and I
use UDP protocol in large networks.
If we restart all clients simultaneously it would create a massive DNS
lookup and crash the network.
So we would have to restart a few of them each time.
I just need rsyslog to contact the new server when necessary.
On Sun, May 31, 2020 at 2:05 AM David Lang via rsyslog
<[email protected]> wrote:
_______________________________________________
rsyslog mailing list
https://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.
