multiple IPs=Problems with Bind9 (with certain ip it works, but status is offline)

Hi,

I lastly installed two additional IPs to my server so I got 3 IPs at all.

By doing this I mentioned problems while my slave dns was getting
notified about new zone info from master because the masters ips
were increased now to 3 IPs.

In past (and now in present) the slave DNS expected to get zone update from
IP1. But after having 3 IPs bind9 from master now selects IP2 to send
notifies and so the slave always refused all updates.

So I went through and found out how to force the master DNS to re-again
using the (old) IP1 by putting:

Code:

listen-on {217.XXX.XXX.126; };
notify-source 217.XXX.XXX.126;

in my named.conf.master template.

that seems to be working
at all I now get a "service warning" in ISPCONFIG that it is offline.

I think this is because bind now listening on hard coded port instead of all
localhost ports *.

Here's whats netstat outputs for DNS:

Code:

tcp        0      0 saXXXXus.net:domain     *:*                     LISTEN     11476/named  

saXXXXus.net is mit RDNS solver.

what should I do? Hack the status-code for Bind?

thx and greetings,
melchior