notify option does not work in Bind 9.x, is this a known bug?

Steven Job list3 at wwwcrazy.com
Mon Feb 21 00:45:02 UTC 2005


Quoting Mark Andrews <Mark_Andrews at isc.org>:

>
>
> 1529.   [bug]           "notify explicit;" failed to log that NOTIFY messages
>                         were being sent for the zone. [RT# 9442]
>

Thanks... That sounds like the same thing.  But is there is difference between
not "logging" the NOTIFY message and actually not sending the NOTIFY message?
My tests show that the NOTIFY messages are not being sent at all. So the log in
this case is showing exactly what is happening.  The strange part is that this
is only occurring when there is a good amount of zones (not just a few).

I'm also noticing a very strange behavior with the "also-notify" with a large
amount of zones (the systems are not being sent the NOTIFY message).  This is
making is virtually impossible to set up Bind on an enterprise level (using IP
anycast) with a large amount of zones.

Is there a suggested work-a-round (server configuration / topology)? Or do most
people go with Nominum's Authoritative Name Server when they want to use IP
anycast (which I guess is what UltraDNS did with Nominum's previous product)?

Thanks,
-Steve



More information about the bind-users mailing list