[rbldnsd] bind()-related bug in rbldnsd

[David Sparks]

> That's why -b option is mandatory now.  It used to bind to 0.0.0.0
> by default, but for UDP it's unreliable - exactly because of the
> reason you outlined.  What I forgot to enforce is explicit binding
> to 0.0.0.0 - the bug is that rbldnsd does not enforce non-zero
> argument for -b option.

Binding to 0.0.0.0 is handy when you only have 1 ip (excluding localhost).
For instance it makes it easier to share the config file among different
rbldnsd servers.  I'm not aware of any disadvantages when doing this?

Could the -b option only be forced on multi-homed servers?


Cheers,

ds