Hi Alexander,
> On 16 Jan 2015, at 23:18, Kunz, Alexander <akunz at wishmedia.de>
wrote:
>
>
> Hello NSD users,
>
> i have seen, that unbound can handle virtual ip addresses, my nsd3
doesn't in my setup. If i set my nsd3 listen to 0.0.0.0 it only bound to the
loacal address but not to the virtual ones. Unbound call this option:
>
> interface-automatic: yes
> >> That acts like '0.0.0.0' (and ::0) but uses (weird) socket
options.
> >> This makes it pick up new interfaces when they are created
(without need
> >> for config edits and restart) or deleted.
> Is there such a function or workaround for nsd? How do you handle virtual
ip address managed by lvs / keepalived?
From the manual:
ip-transparent: <yes or no>
Allows NSD to bind to non local addresses. This is useful to
have NSD listen to IP addresses that are not (yet) added to the
network interface, so that it can answer immediately when the
address is added. Default is no.
This does however require you to know all the IP addresses beforehand, they just
don?t need be active on an interface. Not sure if this works for you, but this
works
for me in my keepalived setup.
Regards,
Arjen
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20150117/557d9afc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3732 bytes
Desc: not available
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20150117/557d9afc/attachment.bin>