Billion Electric Company 30 user manual After Fail Over, Before Fail Over

Authoritative Domain Name Server

192.168.2.2		200.200.200.1	DNS
		1st connection	www.mydomain.com
FTP
			DNS
192.168.2.3	Built-in DNS	nd	200.200.200.1
		2 connection
HTTP		Before Fail Over
192.168.2.2			DNS
FTP		1st connection	www.mydomain.com
192.168.2.3	Built-in DNS	2nd connection	DNS
			100.100.100.1
		100.100.100.1

HTTP

After Fail Over

In the above example, an FTP Server (IP_192.168.2.2) and an HTTP Server

(IP_192.168.2.3) are connected to the Internet via WAN1 (IP_200.200.200.1) on BiGuard 30. A remote computer is trying to access these servers via the Internet, and makes a DNS request. The DNS request (www.mydomain.com) will be sent through WAN1 (200.200.200.1) to the built-in DNS server. The DNS server will reply 200.200.200.1 because this is the only active WAN port. Should WAN1 fail, BiGuard 30 will instead reply with WAN2’s IP address (100.100.100.1), and the remote PC will gain access to the network via WAN2. By configuring BiGuard 30 for DNS Inbound Fail Over, incoming requests will enjoy increased reliability when accessing your network.

Please refer to appendix H for example settings.

2.5.2DNS Inbound Load Balancing

DNS Inbound Load Balancing allows BiGuard 30 to intelligently manage inbound traffic based on the amount of load of each WAN connection by assigning the IP address with the lowest traffic load to incoming requests.

27