Windows Server 2016 Smart DNS (III)

Windows Server 2016 Smart DNS (III)

Our previous articles describe the configuration and introduction of Windows Server 2016 Smart DNS, and we continue today with the previous DNS configuration to highlight the stored procedure, as we mentioned earlier, only in Windows Server 2016 the installation of the DNS service is supported by the relevant DNS operation command, so we need to note that if there are multiple servers in the environment, we need to be created on each server, such as our current architecture, we have more than one DC in the environment, and then at different sites, Do we need to create on each server, the answer is not completely created, why is not completely created, because we understand that as long as the DNS Zone, subnet and other related configuration is stored in the Ad server, but the DNS policy is created on-premises, So if we have more than one server in our environment, after we create a subnet, zone on RWDC, we do not need to do the same on other RWDC or RODC, just perform the relevant DNS policy on the other server. Generally before the understanding of an operation, such as when we created on the RWDC, the RODC data will be synchronized, and then found on the RODC server, a Dnsserverresourcerecord record needs to be modified, so through the relevant PowerShell to modify (General operation first Delete, after new), will execute error, error code 9005, through this error code to understand that there is no permission prompt. Of course, how can the RODC be able to make changes to the data, so our normal operation is to perform modifications on the RWDC, and then naturally synchronized to the RODC server. Where is the road for storage, we explain today, see;

We usually use the command to delete records when the error will be prompted;

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 are generally looking through ADSI, so we need to connect to the relevant area via ADSI to view

Start Running---ADSIEDIT-----connection----Enter your own server information

"Dc=domaindnszones,dc=ixmsoft,dc=com" This partition:

After we link dnszone---cn=microsoftdns--->dc=ixmsoft.com--->cn=zonescopecontainer we can see the two dnszone we created by command

We can see the two Dnsserverresourcerecord records created under the two dnszone we created, but we can edit them directly, but we don't recommend

If we would like to modify the Dnsserverresourcerecord, we recommend using PowerShell to modify, you can 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

Windows Server 2016 Smart DNS (III)