On 01/08/14 15:46, Reindl Harald wrote:
if listen-on {0.0.0.0;}; would work a lot of problems
could go away - keep in mind that on modern systemd
systems a service can bind to 0.0.0.0 even before
the network is started
Most people just use "rndc reconfig". In bind 9.10 the routing socket,
on platforms that support it, will work instantly without being told.
As noted in the bug, the v4 socket API lacks support for setting UDP
source IP on replies. So doing this requires platform-specific hacks.
They don't always work - FreeRADIUS has "udpfromto" code in it, and
people used to report a lot of problems getting it to compile and work
properly.
Binding separate sockets per IP is IMO just as reliable, and is well
tested. If you weren't so opposed to "rndc", you could just call "rndc
reconfig" in whatever network system/dispatch tool you have after IPs -
or wait for bind 9.10.
This is a non-issue IMO.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
