Problem with BIND 8.2.2 NOTIFY

Knut A. Syed Knut.Syed at
Wed Nov 10 13:02:03 UTC 1999

Russell Senior <seniorr at> writes:

> I think I have discovered the problem.  tcpdump is showing that the
> secondary is rejecting the NOTIFY, probably (?) because it is coming
> from a different address than it is expecting.  The host is using IP
> aliasing to attach multiple IP numbers to an interface and the notify
> message is coming from a different IP number than the name server is
> configured to listen on.  Is there a way to force a from address for
> the NOTIFY messages?

query-source address port *;


More information about the bind-users mailing list