S
Systems Administration
Is there an easier way to manage DNS "aliases" that are dependent on site?
Site A: Servername-TEST => 10.1.0.11
Site B: Servername-TEST => 10.99.0.11
I know that on the AD DNS, I create the A record for Site A, and this gets replicated to all DC all sites. However, creating another A record, for the same name and pointing to Site B IP address is not going to work.
I would have to RDP into Site B DC (primary and secondary node) and run the following powershell:
Add-DnsServerClientSubnet -Name "SiteBSubnet" -IPv4Subnet "10.99.0.0/16"
Add-DnsServerZoneScope -ZoneName "Contoso.local" -Name "SiteBZoneScope"
Add-DnsServerResourceRecord -ZoneName "Contoso.local" -A -Name "Servername-TEST" -IPv4Address "10.99.0.11" -ZoneScope "SiteBZoneScope"
Add-DnsServerQueryResolutionPolicy -Name "SiteBPolicy" -Action ALLOW -ClientSubnet "eq,SiteBSubnet" -ZoneScope "SiteBZoneScope,1" -ZoneName "Contoso.local" -Fqdn "eq,Servername-TEST.contoso.local"
Then do ipconfig /flushdns
This would be cumbersome for me to go through 30 DCs (primary and secondary nodes) for 15 site locations... seriously...there has to be a better way to manage this CENTRALLY. Do it all from ONE DC, and force replicate to all other DCs.
SysAdmin
Continue reading...
Site A: Servername-TEST => 10.1.0.11
Site B: Servername-TEST => 10.99.0.11
I know that on the AD DNS, I create the A record for Site A, and this gets replicated to all DC all sites. However, creating another A record, for the same name and pointing to Site B IP address is not going to work.
I would have to RDP into Site B DC (primary and secondary node) and run the following powershell:
Add-DnsServerClientSubnet -Name "SiteBSubnet" -IPv4Subnet "10.99.0.0/16"
Add-DnsServerZoneScope -ZoneName "Contoso.local" -Name "SiteBZoneScope"
Add-DnsServerResourceRecord -ZoneName "Contoso.local" -A -Name "Servername-TEST" -IPv4Address "10.99.0.11" -ZoneScope "SiteBZoneScope"
Add-DnsServerQueryResolutionPolicy -Name "SiteBPolicy" -Action ALLOW -ClientSubnet "eq,SiteBSubnet" -ZoneScope "SiteBZoneScope,1" -ZoneName "Contoso.local" -Fqdn "eq,Servername-TEST.contoso.local"
Then do ipconfig /flushdns
This would be cumbersome for me to go through 30 DCs (primary and secondary nodes) for 15 site locations... seriously...there has to be a better way to manage this CENTRALLY. Do it all from ONE DC, and force replicate to all other DCs.
SysAdmin
Continue reading...