stale cache in alternate views?
Chuck Anderson
cra at WPI.EDU
Mon Jan 10 20:09:40 UTC 2011
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.
More information about the bind-users
mailing list