The setting I just put was "override client settings" does fix the issue with PTR being unable to be created, deleted, or updated automatically in DNS when I typed “ipconfig /registerdns” manually at pc. When I removed the pc out of the domain, the AA and PTR did get deleted automatically and before the change (refer to the setting "override client settings"), AA would be removed but PTR won’t. However, after I removed the pc out of the domain and rejoined it into the domain, the AA and PTR won’t get created in dns automatically. I had to type “ipconfig /registerdns” at the pc to get the pc to register dns and get AA and PTR created. Before the change (refer to the setting "override client settings") , the pc would have AA to be created in DNS automatically right after it joined the domain but no PTR to be created. Therefore, dns on windows 2012 R2/dhcp on cisco ASA firewall still do not work right together.
Any advice to fix the issue with being unable to register dns automatically after the computer joins the domain? By the way, ipconfig /all on the pc does shows the correct dns server ip.
I wonder if the below dynmatic DNS page has something to do with the issue being unable to register dns automatically. What does ddns-2 interval as 0 mean? does it mean no update to be sent? Does it have something to do with dhcp? Please advise!
