stale cache in alternate views?

[Mark Andrews]

The NOTIFY message is only going to one view (external).  The simple
solution is to have the internal view transfer the zone from the
external view.  I posted how to do this within the last month so
check the archives for examples.

Mark

In message <20110110200940.GN28295 at angus.ind.WPI.EDU>, Chuck Anderson writes:
> I'm using bind-9.5.1-P3 (yes, I know it's old).  I have a zone in 
> multiple views.  When I update the zone and reload, the "match-clients 
> { any }" view sees new DNS records right away, but another view 
> doesn't see them for "a while".
> 
> Given this configuration:
> 
> view "global" {
>         match-clients { any; };
> 
>         zone "example.net" {
>                 type slave;
>                 file "/var/named/slaves/example.net.zone";
>                 masters {a.b.c.d;};
>         };
> };
> 
> view "full" {
>         match-clients { a.b.c.0/24; 127.0.0.1; };
> 
>         zone "example.net" {
>                 type slave;
>                 file "/var/named/slaves/example.net.zone";
>                 masters {a.b.c.d;};
>         };
> };
> 
> If a client in the a.b.c.0/24 subnet queries the server, it doesn't 
> see recently added DNS records.  If a client outside a.b.c.0/24 does 
> the same query, it sees the new records immediately after the "rndc 
> reload".
> 
> Anyone know how to change this behavior?
> 
> Thanks.
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org