DNS not configured properly


I have recently upgraded my domain controller from server 2003 to server 2008 R2, this server was acting as my primary DNS server and DHCP server. I have successfully moved all the services over to the new server but I am running into an issue where my users cannot get on the internet anymore unless I put in as a secondary DNS server.  Why is that?

Every client PC I have to do the same thing when before the migration it was working without it.

Who is Participating?
Craig BeckConnect With a Mentor Commented:
That's a bad solution.

You should configure as a forwarder in DNS.  Don't give that as a direct DNS server to domain clients as they'll try to ask for SRV records at
Manjunath SulladTechnical ConsultantCommented:
If you change it to your local DNS IP,

Are you able to do nslookup for google.com and other sites,

If that is working fine, Then there is no problem with DNS configuration,

Also check Firewall settings and DNS Forwarder settings,

Please go through below Technet article for info,


Check this check list is this how you did it?

On a workstation open command prompt and do an IPCONFIG /ALL are all the parameters correct?  i.e. default gateway DNS servers subnet etc.
Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

CervisTECHAuthor Commented:
Yes this is how I did it. the parameters are correct.

The primary DNS server is which is the new Domain Controller. But as a fix I was able to go into DHCP services and add the to the DNS Servers option. This seem to work so now I do not have to go to every PC and add it. But it's funny that I would need to do that in the first place.

CervisTECHAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for CervisTECH's comment #a39836561

for the following reason:

Went into DHCP services and add the to the DNS Servers option.
If is your primary DNS server, do you have any forwarders configured on it?  If not, you should.

What you did MIGHT have helped some, but it could cause random problems.

The DNS resolver on windows will send a DNS lookup request to all DNS servers coded almost at the same time.  It will accept the first answer it gets.  So if you are looking up an internal host name and for some reason your internal DNS server is super busy and happens to answer first with a "no such host" that is the answer your computer will accept.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.