Build a route, DNS, and DHCP server in a simulated Public Network Environment

Build a route, DNS, and DHCP server in a simulated Public Network Environment

Today, we will continue to add a server in the test environment to simulate a vro in the public network environment. This server can simulate common vro functions in the public network as much as possible, it includes three functions: routing, IP Address allocation, and DNS resolution. Others are not configured too much. According to the preceding topology, this virtual machine needs to allocate two NICs, one connecting to the LAN and the other connecting to the WAN.
Next we will allocate IP addresses. For WAN NICs, We will configure IP addresses and masks for them, without the need to configure gateways and DNS.

For LAN NICs, the IP address and mask are also configured. Because it is 10 private network segments, the mask can be used by default.

Then we set up AD because we need to deploy DHCP, and DHCP requires AD to operate normally.

Then we select the DHCP server, DNS server, and remote access.

Then, make sure that the routing function is selected When configuring remote access.

You can set the root domain name when creating an AD, because we will create our own region later. Do not use contoso.com here to avoid conflicts with the SIP domain name, try to build a clean router.

Then we open Routing and Remote Access in the Server Manager-tool, right-click our server name and select "configure and enable Routing and Remote Access ".

Then select Custom configuration in configuration.

Select a LAN route.

After the configuration is complete, start the service and complete the vro configuration.

Next, open the DHCP Management Unit in Server Manager-tools, right-click IPv4 and select create scope.

Then, set a name for the scope, which is mainly used for recognition and easy to remember.

Then you need to set the IP address range, the network segment is 192.168.15.0, And the range is.

No need to add exclusion or delay.

The default lease time is 8 days.

After configuration, understand the configuration.

Next, set the gateway address.

Then, set the DNS server address. There is only one address. Use the router address.

You do not need to set the WINS server because it is a common router and you do not need to use WINS to convert the computer name to an IP address.

After configuration, the scope can be activated.

Next, configure DNS, open DNS in Server Manager-tools, and right-click the forward search area to select the new area.

Create a primary region.

Then select the domain controller in this domain.

To set the region name, we need to set contoso.com here, because our goal is to allow this router to resolve the record to the corresponding IP address in the contoso.com domain, that is, the functions required by the public network router.

Then, only secure dynamic updates are allowed, but we do not need to update them.

After that, we add A new A record in contoso.com, first meet, and resolve it to our front end, 10.0.8.4

Add A record, add the external Web URL address of the front-end, and set it to lfe.contoso.com in this environment.

Then there is the Lyncdiscover, which is used to automatically configure the logon address and resolve it to the front-end IP address.

Then we need to create a forward lookup area, contoso. local, which will not be re-demonstrated here. We must add this area here, otherwise we will not be able to log on externally. Then we add the front-end FQDN record, that is, lfe. contoso. local, and resolve it to the front-end.

Now we have built a router that simulates the public network environment. Next we will connect to the Lync client computer for testing.