Anchor | ||||
---|---|---|---|---|
|
- Independent Deployment Overview
- Deploying a Single Independent Appliance
- Configuration Example: Deploying a NIOS Appliance as a Primary DNS Server
- Cabling the Appliance to the Network and Turning On Power
- Specifying Initial Network Settings
- Specifying Appliance Settings
- Enabling Zone Transfers on the Legacy Name Server
- Importing Zone Data on an Independent Appliance
- Designating the New Primary on the Secondary Name Server (at the ISP Site)
- Configuring NAT and Policies on the Firewall
- Deploying an Independent HA Pair
- Configuration Example: Configuring an HA Pair for Internal DNS and DHCP Services
- Cabling Appliances to the Network and Turning On Power
- Specifying Initial Network Settings
- Specifying Appliance Settings
- Enabling Zone Transfers
- Importing Zone Data
- Defining Networks, Reverse-Mapping Zones, DHCP Ranges, and Infoblox Hosts
- Defining Multiple Forwarders
- Enabling Recursion on External DNS Servers
- Modifying the Firewall and Router Configurations
- Enabling DHCP and Switching Service to the NIOS Appliance
- Managing and Monitoring
- Verifying the Deployment
- Infoblox Tools for Migrating Bulk Data
...
Anchor | ||||
---|---|---|---|---|
|
DMZ
Internal Network
Switch domain name =
corpxyz.com
LAN or
LAN1 Port
Servers for Public Access
Drawio |
---|
The primary and secondary name servers provide DNS protocol redundancy. If one of them cannot respond to a query for the corpxyz.com
Firewall
The NIOS appliance is the primary DNS server for the corpxyz.com domain. It answers queries from the Internet for public-facing servers in the DMZ network.
|
Using primary and secondary name servers provides DNS protocol redundancy, and configuring two DHCP servers as DHCP failover peers provides DHCP protocol redundancy. However, you can only have hardware redundancy if you deploy appliances in an HA (high availability) pair. Should the active node in an HA pair fail, the passive node becomes active and begins serving data, as shown in Figure 6.2. For more information about HA pairs, see About HA Pairs.
Anchor
Internet ISP
Site
This is the same situation as that in Figure 6.1, but the primary DNS server is an independent HA pair to provide hardware redundancy.
Firewall Internal Network
Secondary DNS Server
SwitchLAN (LAN1)
and HA
LAN (LAN1)
and HA
Primary DNS Server (Independent HA Pair)
Active Node
Passive
Servers for Public AccessDMZ
If the active node fails, the passive node becomes active and continues serving DNS.
Drawio | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
When you deploy an independent appliance, you use System Manager to manage the appliance. Though other chapters in this guide contain information that assumes a Grid deployment and describes the Grid Manager GUI, most of the configuration procedures are applicable to an independent appliance, with the following differences:
...