[syslog-ng] "Error resolving hostname" for UDP Destination

[David Hauck]

On Monday, August 24, 2015 7:31 AM, syslog-ng-bounces at lists.balabit.hu wrote:
> sources/destinations are worked on by a set of worker threads, which 
> are not dedicated to a source or destination.
> 
> DNS resolution happens at the input side, so if you have multiple log 
> statements, it will only happen once, right after reception, on the input side.
> 
> however, if you only have one udp() source, that will only use one 
> worker at a time, so if you have multiple threads the others will not be affected.
> 
> hope this helps.

;) Not sure. First off, my UDP DNS resolution concern is in relation to a *destination* definition.

destination d_NAaudit_Prio { file("/var/log/zzz/audit_log" template(t_NAFormat_Prio)); udp("testing" port(514) template(t_NAFormat_Prio)); };

This same destination is used in several log statements, the main one of which is in a fairly complex log statement with multiple junction definitions (see the genesis of this in the following mailing list thread: https://lists.balabit.hu/pipermail/syslog-ng/2014-April/021330.html). 

So it isn't entirely clear to me how a statement definition like this results in a specific thread breakdown... Would isolating this destination to its own thread be as simple as adding "threaded" to the flags option for this destination (and then any of the referenced "log" statements would be running in their own threads), or does this happened by default (in v3.6.x)?

Apologies if I'm missing something obvious here ;).