AW: Cached Information

[Walkenhorst, Benjamin]

Hello,

> So if I understand you correctly, I can set up one view with recursion
> on (for our internal users) which would allow them access to any
> cached data, and also set up another view for external users with
> recursion turned off which would disallow access to any cached data
> since there would be no cached data in this different view that is
> acting like a virtual "nameserver" of itself.

Yes, that is correct. 
To be extra-sure, you can add the following two lines to the external view:
additional-from-auth no;
additional-from-cache no;

(Note that you also have to set "recursion no;" for that view, or else the above
options won't have any effect.)

To quote the BIND 9 ARM:
################################################################################
Specifying additional-from-cache no actually disables the use of the cache 
not only for additional data lookups but also when looking up the answer. 
This is usually the desired behavior in an authoritative-only server where 
the correctness of the cached data is an issue.
################################################################################

Views give a lot of flexibility, but might also take some care to set up correctly and
securely. See http://www.bind9.net/Bv9ARM.ch06.html#view_statement_grammar for more details.

Kind regards,
Benjamin