[rbldnsd] bind()-related bug in rbldnsd

[Anders Henke]

Hi,

I've just come across some strange issue in rbldnsd 0.996a ...

Setup:

rbldnsd3:~# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet 172.19.58.6/32 brd 172.19.58.6 scope global lo:0
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether aa:00:00:17:c4:10 brd ff:ff:ff:ff:ff:ff
    inet 172.19.59.11/24 brd 172.19.59.255 scope global eth0

172.19.58.6 is an IP address reachable via a load balancer,
172.19.59.11 is the management IP address of the box.

If rbldnsd is told to bind to 0.0.0.0 and receives a packet for
172.19.58.6, the answer is sent with 172.19.59.11 as being
the originating address. I see this as a bug.

Workaround: when clearly binding to each IP
("-b 127.0.0.1 -b 172.19.59.11 -b 172.19.58.6", 
rbldnsd answers with the IP address where the query has been received.



Anders
-- 
1&1 Internet AG            System Design
Brauerstrasse 48           v://49.721.91374.50
D-76135 Karlsruhe          f://49.721.91374.225

Amtsgericht Montabaur HRB 6484
Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Andreas Gauger,
Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Norbert Lang, Achim Weiss
Aufsichtsratsvorsitzender: Michael Scheeren