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've just set up an new Windows Server 2008 server who's roles are AD/DNS/DHCP. When a new machine connects to the network it doesn't pick up the dns server automatically and so cannot access the internet.

If I set the primary dns through network properties to the servers IP address it can access the internet. I don't want to have to do this every time though as some are laptops and so access other networks.

Is there something I missed while setting up the server?

share|improve this question
up vote 1 down vote accepted

Double check your DHCP scope options.

share|improve this answer
I've just checked it and the DNS Servers entry in Scope Options is set to Are the client machines then using this IP address (i.e. are they looking locally)? If so I assume I need to change this to the actual IP address? – ADringer Jan 12 '12 at 9:11
@ADringer Correct! – Dan Jan 12 '12 at 9:16
Awesome! Thanks very much! – ADringer Jan 12 '12 at 9:23

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.