Differences

This shows you the differences between two versions of the page.

--- networking:dns:unbound:views [2022/10/08 10:54] – [Networking - DNS - Unbound - Views] peter
+++ networking:dns:unbound:views [2022/10/08 11:19] (current) – peter
@@ Line 3: / Line 3: @@
 Unbound’s views can be used to serve local data depending on the source address a query is received on.
-  * View Name must be unique.
   * Map views to requests using the **access-control-view** option.
   * Views can contain zero or more **local-zone** and **local-data** options.
   * Options from matching views will override global options.
-  * Global options will be used if no matching view is found.
-    * With **view-first yes**, it will try to answer using the global local-zone and local-data elements if there is no view specific match.
 <WRAP info>
@@ Line 28: / Line 25: @@
     name: "anotherview"
     local-zone: "example.com" refuse
+view:
+    name: "evenanotherview"
+    local-zone: example.com inform
+    local-data: 'example.com TXT "this is an example"'
+    local-zone: refused.example.co.uk refuse
 </code>
 <WRAP info>
 **NOTE:**
+  * **name** must be unique.
   * **local-zone** configures a local zone.
@@ Line 53: / Line 57: @@
   * **local-data-ptr** configures local data shorthand for a PTR record with the reversed IPv4 or IPv6 address and the host name.
+  * **view-first** specifies whether to use Global options if no matching view is found.
+    * With **view-first yes**, it will try to answer using the global local-zone and local-data elements if there is no view specific match.
 </WRAP>
@@ Line 116: / Line 124: @@
 <WRAP info>
-**NOTE:**  It doesn’t appear to be possible to use views other than for local data.
+**NOTE:**  It does not appear to be possible to use views other than for local data.
 </WRAP>
@@ Line 132: / Line 140: @@
 https://medium.com/nlnetlabs/response-policy-zones-in-unbound-5d453de75f26
+https://blog.nlnetlabs.nl/client-based-filtering-in-unbound/