In article <[email protected]>, Ben Croswell <[email protected]> wrote:
> What you say is true, but the OP wasn't clear in who owned the record he > wanted to override. I assumed it was someone else's or you would just > change authoritative source that you own. Of course. But it's still the case that you can configure your own resolver as authoritative for someone else's domain, and override their records that way. RPZ provides another way to do this. None of this is considered "cache poisoning", because your overrides are purely local, they don't get into anyone else's cache. > On Feb 14, 2014 10:20 AM, "Barry Margolin" <[email protected]> wrote: > > > In article <[email protected]>, > > Ben Croswell <[email protected]> wrote: > > > > > You can't modify cache. If that was allowed you could cache poison any > > > domain you wanted. > > > > "poisoning" refers to putting incorrect records into the cache of some > > *other* server. If you operate the server itself, you can put anything > > you want into its memory. If you want to override a particular record > > that would normally be cached, just make the server authoritative for > > that name. > > > > -- > > Barry Margolin > > Arlington, MA > > _______________________________________________ > > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > > unsubscribe from this list > > > > bind-users mailing list > > [email protected] > > https://lists.isc.org/mailman/listinfo/bind-users > > -- Barry Margolin Arlington, MA _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/bind-users
