It is highly recommended that the provided host names are used.
Disable content caching and AV scan in the proxy for those connection to avoid corruption of the definition files.
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
However, the reverse DNS entries ("PTR" Records) are not.
If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.
Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).
Step 2) Live Update Installer Assume the wrong Live Update version is installed on the system, locate the Live Update installer shipped with your release of Endpoint Protection as per above.
Step 3) Remove Live Update and install the correct version for SEP 12.1 - Uninstall "Symantec Live Update" from the Windows Control Panel, - Reboot the server, - Install the Live Update shipped with your release of Endpoint Protection.On the DNS tab enable DNS dynamic updates and set to "Always dynamically update..." Also enable Dynamic Update for clients that do not request updates.1a) Even if these are enabled, you might need to make sure the DHCP server has permissions to update DNS records.The only thing I had to do after this was, flush the dns entries on the clients with: ipconfig /flushdns After this they have poped up in my reverse lookup zone. The fix of adding the DHCP server to DNSupdateproxy group solved my issues. As a best practice, ensure that the EPM is upgraded to the very latest release of Endpoint Protection 12.1.Step 4) Cleanup the Live Update Catalog and Re-register Endpoint Protection Manager with Live Update.