Saturday, September 10, 2016

windows server 2016 - Should PTR for domain controller be automatically created?

Reverse look up for my domain controller doesn't work.




Invoke-Command -Credential $Cred -VMName $vmname  -ScriptBlock {Install-WindowsFeature DNS -IncludeManagementTools}
Invoke-Command -Credential $Cred -VMName $vmname -ScriptBlock {Add-DnsServerPrimaryZone -Name gj2corp.com -ZoneFile 'gj2corp.com.dns'}
Invoke-Command -Credential $Cred -VMName $vmname -ScriptBlock {Add-DnsServerPrimaryZone -NetworkID 192.168.64.0/24 -ZoneFile '64.168.192.in-addr.arpa.dns'}
Invoke-Command -Credential $Cred -VMName $vmname -ScriptBlock {Add-DnsServerForwarder -IPAddress 8.8.8.8 -PassThru}
Invoke-Command -Credential $Cred -VMName $vmname -ScriptBlock {Set-DnsServerPrimaryZone -Name gj2corp.com -DynamicUpdate 'NonsecureAndSecure' -PassThru}
Invoke-Command -Credential $Cred -VMName $vmname -ScriptBlock {Set-DnsServerPrimaryZone -Name '64.168.192.in-addr.arpa' -DynamicUpdate 'NonsecureAndSecure' -PassThru}


If I manually add a PTR record for it, then it works. Should I have to add it manually?




Tried it on Windows 2016 and 2019

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...