nsd users - Oct 2005 - missing query-source/transfer-source in nsd

Hi,

We are in the process of switching our master nameserver from bind to nsd.
Therefor we are running both bind and nsd on the same machine, each on their
own IP address. We need bind because the old IP is used for recursing.

In named.conf, I have:

         query-source address 193.110.157.130 port 53;
         transfer-source 193.110.157.130;

My nsd init script adds "-a 193.110.157.135" to the nsd daemon startup
options.

The problem I am seeing now is that nsd is not using 193.110.157.135 for
sending notifies to its secondaries. Instead, it takes the default
('first')
IP address, which happens to be 193.110.157.130.

Are there any plans to add such a feature to nsd? Especially people who want
to migrate from bind to nsd are likely to run both of them on the same server
for a while (or even permanently if they need bind to recurse).

As a workaround, I've added both IP's as masters in the secondaries'
named.conf.

Paul
-- 

"Happiness is never grand"

 	--- Mustapha Mond, World Controller (Brave New World)

[On 13 Oct, @05:52, Paul Wouters wrote in "missing  query-source/transfer
..."]
> 
> Hi,
> 
> We are in the process of switching our master nameserver from bind to nsd.
> Therefor we are running both bind and nsd on the same machine, each on
their
> own IP address. We need bind because the old IP is used for recursing.
> 
> In named.conf, I have:
> 
>          query-source address 193.110.157.130 port 53;
>          transfer-source 193.110.157.130;
> 
> My nsd init script adds "-a 193.110.157.135" to the nsd daemon
startup
> options.
> 
> The problem I am seeing now is that nsd is not using 193.110.157.135 for
> sending notifies to its secondaries. Instead, it takes the default
('first')
> IP address, which happens to be 193.110.157.130.
> 
> Are there any plans to add such a feature to nsd? Especially people who
want
> to migrate from bind to nsd are likely to run both of them on the same
server
> for a while (or even permanently if they need bind to recurse).
> 
> As a workaround, I've added both IP's as masters in the
secondaries' named.conf.
my guess is that this is a bug, a long time ago there was something
simular with regard to sending queries from a different ip address.
The same fix should apply here (I hope :))

--
grtz,
  - Miek

 http://www.miek.nl                      http://www.nlnetlabs.nl
  PGP Key ID: 3880 D0F6
 fingerprint: 6A3C F450 6D4E 7C6B C23C  F982 258B 85CF 3880 D0F6
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20051017/020f98c2/attachment.bin>