Hello there,
To resolve this simply delete the record out of your host's file which is found in %windir%\system32\drivers\etc.
Among a number of causes, this could be the result of having a record for the servers IP address in your hosts file which resolves to a name that does not exist in Active Directory. Since DHCP does a reverse lookup on the binding IP (your internal server’s IP) to discover the computer object in AD to authorize it for DHCP services, a return of an invalid hostname will cause the authorization to fail. You can verify this as well by performing a ping test as follows to verify the bad resolution of the servers IP to its name. On this example, we will assume that the server’s internal IP is 192.168.16.2 and the server name is SERVER.CONTOSO.LOCAL.
Unable to Manage DHCP When an Invalid Name Record Exists in your Hosts File https://techcommunity.microsoft.com/t5/windows-server-essentials-and/unable-to-manage-dhcp-when-an-invalid-name-record-exists-in-your/ba-p/397109
Hope this resolves your Query !!
--If the reply is helpful, please Upvote and Accept it as an answer–