The following steps are required.
Configure NAT maps for your public IPs referenced here:
NAT Mappings also known as 1-to-1 NAT allows internal hosts, such as web server and mail server etc., behind Peplink Balance to communicate to the Internet via all protocols. With 1-to-1 NAT, you can:
For inbound traffic, forwarding all TCP/UDP/IP protocols to the host behind the Peplink units.
For outbound traffic, you can specify a Public IP address which you defined as "Additional Public IP" via WAN Settings as the source IP address.
The followings are two scenarios of configuring 1-…
Set up the integrated DNS server for your domains referenced here:
Inbound Load Balancing distributes inbound data traffic over multiple WAN links to computers behind Peplink Balance. Peplink Balance 210 or above have a built-in DNS server that enables this functionality.
You can configure Peplink as Authoritative DNS for a domain such as "foobar.com" via build-in DNS server for inbound link load balancing.
Note: Configure the Peplink as Authoritative DNS for domain "foobar.com" means Peplink will hold all DNS records (A, MX, CNAME, TXT etc) for the domain.…
After testing this you would set up at least two name servers in your domain registrar pointing to the Balance WAN IPs configured for Authoritative DNS.