DNS Policy On WinSrv 2019

heyz 0 Reputation points
2023-09-12T04:00:23.7533333+00:00

I have read ‘DNS Policy Scenario Guide’ https://learn.microsoft.com/en-us/windows-server/networking/dns/deploy/dns-policy-scenario-guide .

I Create a test domain named test.com 、two DCs &DNS (DC01 :192.168.10.10 & DC02:192.168.10.20) And Several Clients。

I Create two A records in dns:

www--192.168.100.100

www--192.168.200.100

Then I Create some DNS policys on DC01 :

Create the DNS Client Subnets:

Add-DnsSererClientSubnet -Name "CS" -IPv4Subnet "192.168.0.0/24"

Add-DnsSererClientSubnet -Name "WC" -IPv4Subnet "192.168.20.0/24"

Create the Scopes of the Zone:

Add-DnsServerZoneScope -ZoneName "test.com" -Name "CSScope"

Add-DnsServerZoneScope -ZoneName "test.com" -Name "WCScope"

Add Records to the Zone Scopes:

Add-DnsServerResourceRecord -ZoneName "test.com" -A -Name "www" -IPv4Address "192.168.100.100" -ZoneScope "CSScope"

Add-DnsServerResourceRecord -ZoneName "test.com" -A -Name "www" -IPv4Address "192.168.200.100" -ZoneScope "WCScope"

Create the Policies:

Add-DNSServerQueryResolutionPolicy -Name "CSPolicy" -Action Allow -ClientSubnet "eq,CSSubnet" -ZoneScope "CSScope,1" -ZoneName "test.com"

Add-DNSServerQueryResolutionPolicy -Name "WCPolicy" -Action Allow -ClientSubnet "eq,WCSubnet" -ZoneScope "WCScope,1" -ZoneName "test.com"

I run nslookup www 192.168.10.10 on Client01 Which IP is 192.168.0.10, it returns 192.168.100.100

I run nslookup www 192.168.10.10 on Client02 Which IP is 192.168.20.10, it returns 192.168.200.100

but when i run nslookup www 192.168.10.20 on Client01 &Client02,it retuens 192.168.100.100 & 192.168.200.100,

it seems that the dns policy can't sync from 192.168.10.10 to 192.168.10.20 , the dns zone "test.com" is a Active Directory Integrated Zone 。

My question is How to sync the dns policy between DNS Servers In my scenario ? Thanks !

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,445 questions
0 comments No comments
{count} votes