Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a question that probably seems kind of stupid but I can't find a definitive answer from google.

In Microsoft's DHCP Server service, and if you are running AD, you can "authorize" a DHCP server.

I'm guessing that means that if a DHCP server is not authorized, and joined to the domain, it won't respond to DHCP requests correct?

Also, does it need to have it's name in DNS for it to actually function properly? For example ->
I know it's recommended, but what are the ramifications if you don't have it?

share|improve this question

Although it is not recommended, you can use a stand-alone server as a DHCP server as long as it is not on a subnet with any authorized DHCP servers. When a stand-alone DHCP server detects an authorized server on the same subnet, it automatically stops leasing IP addresses to DHCP clients Please check this link for more details in this topic..

DNS is not necessary for DHCP service. But it's critical service if you are running AD so most probably any member server/domain controller will [re]register yourself in DNS while join domain or Netlogon service restart

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.