NIOS-DDI-EXPERT practice question 9 of 15

The standard or recommended architecture for NIOS DNS views is "one member, one view".

Full set: 80 questions
Answer options
A:

A. True

B:

B. False

Correct Answer:
TRUE
Explanation

The "one member, one view" architecture is the standard and recommended best practice for deploying Infoblox NIOS DNS views, particularly in environments requiring a high degree of security and administrative separation (e.g., split-horizon DNS with internal and external views). This model dedicates a specific Grid Member (or an HA pair) to serve a single DNS view. This approach provides the strongest possible isolation, preventing potential data leakage between views and simplifying configuration, management, and troubleshooting. While it is technically possible for a single member to serve multiple views using match clients lists, the recommended architecture for security and robustness is to physically or logically separate the members serving different views.

Why Incorrect

The "False" option is incorrect because it confuses technical capability with recommended best practice. Although a NIOS member can be configured to serve multiple views, this is not the standard or recommended architecture due to the increased complexity and potential security risks of mixing traffic and data from different security zones (e.g., internal and external) on a single appliance. The principle of least privilege and defense-in-depth strongly favors the segregated "one member, one view" model.

References

1. Infoblox NIOS Administrator Guide, 9.0: In the "Configuring DNS Views" chapter, the guide details how views are used to provide different answers to different clients. The entire premise of views is data segregation. The guide states, "You can create multiple DNS views and assign them to different members and zones... When you have multiple views, you can provide different DNS data to different clients, depending on the view to which the client belongs." The architectural recommendation that follows from this principle is to assign distinct members to distinct views for maximum security. The configuration examples for split-horizon DNS implicitly support this by showing separate configurations for internal and external name servers.

2. Infoblox Deployment Guide: DNS and DHCP: This guide provides architectural best practices. In sections discussing secure DNS deployments, it consistently illustrates architectures where internal DNS servers are separate from external (DMZ) DNS servers. This physical and logical separation directly maps to the "one member, one view" concept, where one set of members serves the "internal" view and a completely separate set of members serves the "external" view.

3. Infoblox White Paper: Best Practices for External DNS Security: This document explicitly recommends isolating external DNS servers from the internal network and internal DNS infrastructure. It states, "External DNS servers should be dedicated to their purpose and should not perform other DNS roles, such as internal resolution or recursion for internal clients." This directly supports the principle of dedicating a member to a single view (in this case, the external view) for security purposes.

Scroll to Top