I have failover cluster with 2 nodes .Both nodes have windows server 2016 and i was configured DNS Aging and Scavenging (Cleanup Stale DNS Records). But unfortunately cluster name and listener dns records have been deleted and not created automatically .. so how to configure failover cluster to register its records automatically ? I tried to give failovercluster permission on dns but it didn't register dns automatically .. I can do it manual with power shell command but I need it to be automatically.
Asked
Active
Viewed 1,892 times
1
-
Why not set static records ? – Overmind Dec 03 '20 at 09:52
-
The cluster is created it during configuration . and I configured dns to delete records that didn't update their records for 7 days .. unfortunately cluster name and listener is deleted after enabling this option in dns .. can you explain how dns automatically register client for example if I put ip for pc and dns ( dc dns server) so its register automaticlly in dns records .. but if I deleted it .. it didn't show again automatically .. so how I control it ? – Mostafa Elgaml Dec 03 '20 at 10:06
-
That part automatically works "out of the box" without much administrative overhead. Unless something was intentionally done to the contrary. Does the zone allow updates ? That may be a problem. – Overmind Dec 03 '20 at 10:39
-
yes , It allows update (secure and none secure) . if I updated IP address the record is updated automatically , but I deleted it . it not created automatically . – Mostafa Elgaml Dec 03 '20 at 11:12
1 Answers
0
This question has a lot to do with debugging/analysis.
Is your DNS-Client service running?
Did you check if in the registry the DisableDynamicUpdate is set to 0?
Check here.
In the network interface is the checkbox enabled to register the connection in DNS?
PowerShell for this: Set-DnsClient -InterfaceIndex "Name Connection" -RegisterThisConnectionsAddress $true -UseSuffixWhenRegistering $true
You can check here for more hits: AD Dynamic DNS Updates not triggering on clients
unNamed
- 523
- 2
- 10