A reoccurring issue where the Mac laptops in an environment lose their local hostname and reverts to default hostname of "Macbook-pro." This happens when going from Ethernet to WiFi and back, and creates a conflict with the hostname (e.g. testmacbook) and then reverts the name to the default of "Macbook-pro." When this happens to several machines, it then creates conflicts between "Macbook-pro" hostnames, giving a warning message when users log in about a conflict, and increments their local hostname to "Macbook-pro-2", "Macbook-pro-3", etc.Cause:
This happens because the environment was set up with DHCP, providing dynamic DNS registration with name protection, and did not properly secure the 'DnsUpdateProxy' group. This meant that the DHCP service account that was supposed to be registering dynamic DNS entries does not work as expected.Resolution:
In order to correct this issue, an Administrator will need to make sure to properly configure DynmaicDNS and making sure to secure the DnsUpdateProxy group by running the following command: dnscmd /config /OpenAclOnProxyUpdates 0
Once complete, restart the DC/DNS/DHCP server, and the issue should be resolved.
The following link is provided as a courtesy to explain in more detail.https://blogs.msmvps.com/acefekay/2016/08/13/dynamic-dns-updates-how-to-get-it-to-work-with-dhcp-scavenging-static-entries-their-timestamps-the-dnsupdateproxy-group-and-dhcp-name-protection/
For additional information not covered in this guide or troubleshooting assistance, please review Centrify Online Help
or visit the Centrify Customer Portal at support.centrify.com