Radware Alteon Application Manual page 728

Alteon Application Switch Operating System Application Guide
Global Server Load Balancing
>> Virtual Server 2 http Service# apply
>> Global SLB# cur
6. Examine the resulting information. If any settings are incorrect, make and apply any appropriate
changes, and then check again.
>> Global SLB# /cfg/slb/cur
7. Save your new configuration changes.
>> Layer 4# save
Note: Configuration for the Tokyo site is now complete.
Example Standalone DNS Server Configuration
The following is the DNS server functionality:
• It is possible to configure two (2) NS records: NS1 with Alteon1 interface IP address and NS2
with Alteon2 interface IP address.
• If Alteon2 is alive, Alteon1 is down (domain name cannot be resolved by using NS1) and DNS
server switches to NS2.
• If Alteon1 is alive, Alteon2 is down (domain name cannot be resolved by using NS2) and DNS
server switches to NS1.
• If Alteon1 is alive (NS1 is used), Alteon2 was down. After that, Alteon2 is alive and DNS server
continues to use NS1.
• If Alteon2 is alive (NS2 is used), Alteon1 was down. After that, Alteon1 is alive and DNS server
continues to use NS2
• The round-robin algorithm for DNS server can be disabled.
To configure a Microsoft Windows 2003 DNS Server
The DNS server is configured to resolve domain name (e.g. "geored.com") into active Alteon virtual
IP address which represents active MCS system (Alteon1 VIP1, Alteon1 VIP2, or Alteon2 VIP1,
Alteon2 VIP2).
1. Open the DNS console.
2. Create a primary forward lookup zone "com".
3. Create a delegation in zone "com": Delegated domain "geored"; FQDN - "geored.com".
4. Add the first resource record: FQDN—Alteon1 interface IP address (which is set up by using the
command
/cfg/l3/if 1
5. Add second resource record: FQDN—Alteon2 interface IP address; IP address—Alteon2
interface IP address. This example configuration is shown in
729:
728
); IP address – Alteon1 interface IP address.
Figure 122 - DNS Console, page
Document ID: RDWR-ALOS-V2900_AG1302