Anchor | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
SiteThe ISP hosts a secondary DNS server for the corpxyz.com domain.
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.
DMZ
Internal Network
Switch domain name =
corpxyz.com
LAN or
LAN1 Port
Servers for Public Access<place for figure>
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
Figure 6.2 Independent HA Pair 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.
<place for figure>
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:
...