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

Windows Server 2016 Intelligent DNS (4)

Our previous articles introduced the relevant configuration and introduction of Windows Server 2016 intelligent DNS. Today, we continue the previous DNS configuration to focus on stored procedures. As we mentioned earlier, only the DNS service installed under Windows Server 2016 supports relevant DNS operation commands, so we all need to pay attention to the fact that if there are multiple servers in the environment. Do we need to create it on each server? for example, in our current architecture, we have multiple DC in our environment, and then in different sites, do we need to create on each server? the answer is not completely created, why not, because we know that as long as DNS Zone, Subnet and other related configurations are stored in the AD server, but DNS Policy is created locally. Therefore, if there are multiple servers in our environment, after we create a subnet and Zone on RWDC, we do not need to do the same on other RWDC or RODC, we just need to perform the relevant DNS Policy operation on other servers. Generally speaking, you have done an operation before you do not understand it. For example, after we create it on RWDC, the data of RODC will also be synchronized, and then you will find that a DnsserverResourceRecord record on the RODC server needs to be modified. Therefore, if you modify it through the relevant Powershell (the general operation is deleted first, then create a new one), you will execute an error, Error Code 9005. Through this Error Code, you can learn that there is no permission. Of course, how can RODC make changes to the data, so our normal operation is to make changes on RWDC, and then naturally synchronize to the RODC server. As to where the road strength of storage is, let's explain it today, as shown in the following picture.

We usually give an error when we delete a record through a command.

Remove-DnsServerResourceRecord-ZoneName "ixmsoft.com"-RRType "A"-name "web"-RecordData "192.168.10.200"-ZoneScope "USSubnetScope"

If we want to view the data in the background, we usually view it through ADSI, so we need to connect to the relevant area through ADSI to view.

Start running-ADSIEDIT- connection-enter your own server information

The partition "DC=DomainDnsZones,DC=ixmsoft,DC=com":

When we link to DNSZone-CN=MicrosoftDNS--- > DC=ixmsoft.com--- > CN=ZoneScopeContainer, we can see the two DNSZone we created with the command.

We can see the two DNSZone records created under the two DNSServerResourceRecord records created. Of course, we can edit and modify them directly, but it is not recommended.

If we want to modify DNSServerResourceRecord normally, it is recommended to use Powershell to modify it. Please refer to the following command

$Record = Get-DnsServerResourceRecord-ZoneName ixmsoft.com-Name www-ZoneScope USZoneScope$NewRecord = $Record.Clone () $NewRecord.RecordData.IPv4Address = '192.168.20.20'Set-DnsServerResourceRecord-ZoneName ixmsoft.com-ZoneScope USZoneScope-OldInputObject $Record-NewInputObject $NewRecord

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.