On Thu, Feb 25, 2016 at 9:37 AM, Barry Kaplan <[email protected]> wrote:
> Ok, is this something that would be considered for change? In our
> environment there is no guarantee that nodes will remain on the same IP. For
> this we use consul and dnsmasq to lookup DNS names.
>

Sure, we would consider accepting a pull request for this. Remember
that the ossec processes generally chroot to /var/ossec, and the
resolution should finish before the chroot (or everything needed to
resolve the name copied to /var/ossec?).

> For now I will hard code server_hostname to the DNS of the ossec server. At
> least that value exists when the agent starts. But when the ossec server
> dies (AWS nodes die all the time) I will have update and restart every
> agent.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "ossec-list" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"ossec-list" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to