DNS views or Domain views serve different responses to DNS queries based on various criteria, most commonly the source of the query or the host accessing it. This indicates that the DNS server can present one set of DNS information to one group of clients and a different set to another group, based on predefined views.
DDI enables you to create multiple views and name them for better identification
Select the DNS menu the left menu bar. Now select Views from the submenus that appear on the inner menu bar.
Select the DNS menu from the menu bar along the left side of the screen.
From the submenus that appear, choose Views.
If views have never been enabled for any of the existing zones, the screen will display the message No View Available.
Clicking on the Enable View button now will move all the existing domains to a Default view. Clicking Yes will create a Default View entry in the Views page. Here you can see under the match client field holding the value any, indicating this configuration will apply to all clients.
Default View
Default view for a domain refers to the unnamed or implicit view that is used when no specific view has been defined for a set of DNS queries. In the default view, BIND handles DNS queries as any standard DNS server would, without applying different rules or data sets based on the query source. It simply serves the DNS zones and records as configured.
In more complex configurations where named views are used, the default view can still exist. It would handle any queries that don't match the criteria of the named views. For example, if there are views for internal and external networks, the default view could handle queries from sources not covered by these specific views.
To create a named View, click on the Add View button in the top right corner. The Create View page appears.
Input a name for the new View in the designated field.
For the Match Clients field, input the list of IP addresses or specify named Access Control Lists (ACLs) as required.
Select the DNS options relevant for your selection of clients.
Once all the necessary information is provided and options are selected, click Save.
Recursion: Controls whether the server will perform recursive queries for clients using this view. This can be enabled for internal clients and disabled for external ones to prevent abuse.
Forwarders: Specifies different upstream servers for resolving DNS queries for clients that match the view. This can redirect query traffic based on client type or requested domain.
Response Policy Zone (RPZ): Implements response policy service, allowing the server to modify or block DNS responses based on policies.
Order of Precedence: If a client matches multiple views, the order in which the views are defined in the configuration file determines which one finally applies.
Allow-recursion, allow-query, allow-transfer: These options within a view can be used to control which clients are allowed to perform recursive queries, make queries, or request zone transfers, respectively.
DNSSEC Validation: Controls whether DNSSEC validation is performed for the clients that match the view. This might be enabled for external views to provide DNSSEC security for internet clients.