Another option is to stand up a DNS server that knows how to do something like BIND 9&#x27;s Response Policy Zone [0][1].<p>Although figuring out how to propagate RPZ changes to them isn&#x27;t exactly straightforward (more on this below), if you&#x27;re using BIND, you can set up views that match certain clients and provide one mix of RPZs to one set, and another to another set.<p>On updating RPZs in a view (warning: BIND 9-specific instructions follow) :<p>So, BIND has this nifty option for a zone called &quot;in-view&quot;. This lets you say &quot;The data for this particular zone lives in this other view, so when requests come in for this zone, in this view, use the data in this other view.&quot;. It might sound complicated, but it&#x27;s really just a pointer to a pre-existing zone definition. This lets you define your master zones in one big &quot;zone definition&quot; view, and have client-specific views refer back to those definitions.<p>However, you can&#x27;t use in-view with RPZs. Why? Who knows? [2] But, what you <i>can</i> do is this:<p>* Create one unique RNDC key per view<p>* Add an allow-notify and match-clients entry in each view with that view&#x27;s key<p>* In the appropriate views, add a slave zone definition for each relevant RPZ, with localhost as the master, and whatever is your usual domain xfer key as the key [3]<p>* Back up in your &quot;zone definition&quot; view, add to your also-notify list for each master RPZ definition an entry for localhost and each view key. [4] Having an ACL <i>just</i> for these RPZ slaves cleans up the RPZ definitions.<p>Now you have dynamically updatable host blocking that can be deployed on a per-host basis, if you like. It&#x27;s <i>initially</i> a bit more work than managing a local hosts file, but you can easily apply host blocking lists to any set of machines on your LAN, and you can programmatically update the RPZ lists with tools like nsupdate.<p>[0] <a href="http:&#x2F;&#x2F;jpmens.net&#x2F;2011&#x2F;04&#x2F;26&#x2F;how-to-configure-your-bind-resolvers-to-lie-using-response-policy-zones-rpz&#x2F;" rel="nofollow">http:&#x2F;&#x2F;jpmens.net&#x2F;2011&#x2F;04&#x2F;26&#x2F;how-to-configure-your-bind-reso...</a><p>[1] <a href="http:&#x2F;&#x2F;www.zytrax.com&#x2F;books&#x2F;dns&#x2F;ch7&#x2F;rpz.html" rel="nofollow">http:&#x2F;&#x2F;www.zytrax.com&#x2F;books&#x2F;dns&#x2F;ch7&#x2F;rpz.html</a><p>[2] RPZs are handled just like regular zones in <i>every</i> other way except for this one. It&#x27;s a bit frustrating.<p>[3] This is actually less burdensome than it sounds, as you can write these slave zone definitions once and include the files containing the definitions in whatever view needs them.<p>[4] That is, if you had three views, your also-notify list would have something like the following new entries: <i>127.0.0.1 key &quot;view1-key&quot;; 127.0.0.1 key &quot;view2-key&quot;; 127.0.0.1 key &quot;view3-key&quot;;</i> You can have entries for <i>just</i> the views that use a given RPZ, but it doesn&#x27;t hurt to have one ACL that notifies <i>all</i> views when any RPZ data changes.