Paul Wouters
2010-Feb-22 18:02 UTC
[nsd-users] internal nsd-xfer calls by nsd not using ip-address: as source?
Hi, I'm looking at a bug report with nsd. This is a machine with two interfaces configured within the same subnet. nsd is configured with ip-address: to one of them. When nsd responds to a NOTIFY, it seems to be using ANY instead of the ip-address: configured. This causes the client to need to add this second ip to their ACL lists. I'm looking at the code, but the code path for this is non-trivial. So no patch from me yet. Paul
W.C.A. Wijngaards
2010-Feb-23 07:33 UTC
[nsd-users] internal nsd-xfer calls by nsd not using ip-address: as source?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Paul,
Is this about a need for this option?
zone:
# set local interface for sending notifies and zone transfers
outgoing-interface: 10.0.0.10
Best regards,
Wouter
On 02/22/2010 07:02 PM, Paul Wouters wrote:>
> Hi,
>
> I'm looking at a bug report with nsd. This is a machine with two
interfaces
> configured within the same subnet. nsd is configured with ip-address: to
> one
> of them. When nsd responds to a NOTIFY, it seems to be using ANY instead of
> the ip-address: configured. This causes the client to need to add this
> second
> ip to their ACL lists.
>
> I'm looking at the code, but the code path for this is non-trivial. So
> no patch
> from me yet.
>
> Paul
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEUEARECAAYFAkuDhMAACgkQkDLqNwOhpPiTTwCfb3VZysFid0fh7J1YMGqAfJj1
SDEAljvAwoh7iyg+pAuldGd8nT7KCAg=he4h
-----END PGP SIGNATURE-----