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

> Quoting Mark Andrews <Mark_Andrews@isc.org>:
>
> >
> >
> > 1529. [bug] "notify explicit;" failed to log that NOTIFY messag
> es
> > were being sent for the zone. [RT# 9442]
> >
>
> Thanks... That sounds like the same thing. But is there is difference betwee
> n
> 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 thi
> s
> is only occurring when there is a good amount of zones (not just a few).

I'm sure they are being sent unless you have a configuration error.

Set a port with notify-source and you should be able to pick them
up on a packet trace easily. Note they are rate limited along
with refresh queries (same queuem, serial-query-rate <integer>;)

> 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 I
> P
> anycast) with a large amount of zones.
>
> Is there a suggested work-a-round (server configuration / topology)? Or do mo
> st
> 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
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org