ShiNNinG.net

I was trying to install and configure DHCP services on a sub-domain in my AD environment. After installing the role for DHCP I attempted to authorize the service. At first the snap-in stated that the authorization was successful. But under further investigation the IPv4 and IPv6 scopes were not being activated. In fact, the DHCP service itself was starting and then immediately stopping. When I attempted to re-authorize the service I received an “access denied” message. I saw some funky errors in the logs regarding how the system could not find the Enterprise server. I then logged in as a root domain Enterprise Admin, reinstalled the DHCP role, and attempted to authorize the service, this did not work either. But now I was at least getting a new error in the logs, a 1046

The DHCP/BINL service on the local computer, belonging to the Windows Administrative domain XXX, has determined that it is not authorized to start. It has stopped servicing clients. The following are some possible reasons for this: This machine is part of a directory service enterprise and is not authorized in the same domain. (See help on the DHCP Service Management Tool for additional information).
This computer cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to a directory service enterprise on which the local computer is not authorized.
Some unexpected network error occurred.

At quick google of the issue turned up a MS post . The instructions stated to use the Manage Authorized Servers dialog to actually perform the authorization instead of just using the context menu. In the dialog I deleted the entry for the local DHCP server and added it back in to authorize. For some reason this did the trick and the DHCP service immediately started. Weird.