Shulou(Shulou.com)06/02 Report--

Windows Server native DNS Zone to implement intelligent parsing

As we introduced in the previous articles, Windows Server 2016 Intelligent DNS configuration introduction document, the most basic premise of configuring intelligent DNS is Windows Server 2016. Can't it be implemented if you can't upgrade in the environment or you can't get Windows Server 2016 for other reasons? In fact, it can also be implemented, but it can only achieve a small number of functions, such as different DNS parsing returns different addresses, and other access control cannot be done, so you can only return different addresses to different DNS accesses at the lowest level. How do you do that?

For example, our local DNS is the Windows Server 2012 version of the service system. We finally hope that visiting the xll,byssoftcom within the company will return the internal address: 192.168.100.32, the branch users will visit the xll.byssoft.com to return the public network address, and the external network users will definitely return the public network address, because the branch must synchronize the data with the headquarters through × × ×. The branch must also have its own RODC or DNS server, which is very easy to configure, as shown below:

Let's first open the DNS management-forward region-create a new zone.

DNS:192.168.5.61

Create a new primary area and uncheck-Storage area in AD

We define the zone name: the format of the zone name must be the FQDN of the domain name we visit

For example, the domain name we visit is xll.byssoft.com, so the domain name here must also be in the format of access domain name.

You can create a new file by default.

Dynamic updates are not allowed

The creation is complete:

We create a new host record in the newly created xll.byssoft.com area

The address to be accessed is defined as 192.168.100.32. The hostname must be empty. If it is empty, it defaults to the parent name, that is, xll.byssoft.com.

Creation completed

Then the local creation is completed, and then on other DNS (192.168.5.65) servers, we also create a new xll.byssoft.com zone, but the newly created host record IP address needs to point to the public network, or we can add it to the default byssoft.com zone. However, it is recommended to create a new A record in the new DNS area of xll.byssoft.com.

Let's skip the new area, just like the steps above.

The name of our new zone must also be xll.byssoft.com

Create a new host record in the xll zone, and the name of the host record must also be empty

New construction completed

And then we tested it.

We first point the DNS of the test machine to the first server: 192.168.5.61, and return the internal address: 192.168.100.32

Then point the DNS of the test machine to the second server: 192.168.5.65, and return the internal address: 10.100.24.22

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.