[Last Call] Learn how to a build a cloud-first strategyRegister Now


DNS server Locking up

Posted on 2009-04-29
Medium Priority
Last Modified: 2012-05-06
 I have a DHCP server that is delivering a range of 172.16.1.* to my clients. The DHCP server is also sending out information about my DNS and WINS servers. My first DNS and WINS server is and second is I have also listed a couple of external DNS servers to help resolve things as needed. I'm having the problem of my internal DNS serves not resolving an address that I know it has, then the external DNS servers respond with an external address to an internal link. What I mean by this is that I have an address like me.help.com that in resolving to on the internal DNS server and on the external it's My clients are getting the external address about once out of 20 calls. I have tried shutting down each of my DNS servers to see if one of my servers was locking up but no luck. Does anyone have any ideas what the problem could be that is causing my DNS servers not to respond?

Question by:Amirsys
  • 3
LVL 15

Accepted Solution

zelron22 earned 1800 total points
ID: 24260942
You should not be handing out external DNS servers to your windows domain clients.  They need to find an active directory aware DNS server, and ONLY an active directory aware server (same for servers that are domain members with static IPs).  

Your DNS server should then be set to forward Internet DNS requests out to an internet DNS server.  This is set in the DNS console, under server properties, forwarders tab.

The DNS servers TCP/IP settings on its NIC should only point to itself (using its IP address, not the loopback).


Author Comment

ID: 24261096
Would this cause the client to also feel like it locks up and I have to do a ipconfig /release and /renew to get the internal address?

Author Comment

ID: 24261228
The other question is also that I have had this configuration running for over a year with no problems. I do see how it could but just not understanding why it started to cause problems now.
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 200 total points
ID: 24261560
The reason is that the clients might not have used the external IP addresses to try to resolve internal names until now. Or you might have a higher volume of DNS requests and now they are getting passed down the line.

You should never have external DNS servers listed in your internal domain's clients or server's TCP\IP properties. Even if the clients have two internal DNS servers listed before the external DNS servers the clients can still use those DNS servers. When you have multiple DNS servers listed in the TCP\IP properties the clients can use any of them it will not just look at the primary for resolution only. If the Primary DNS server doesn't come back with a request fast enough for the client the client will start going down the line of DNS servers it has.

Author Comment

ID: 24261941
I have made the changes and will see if the problem goes away.


Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Learn about cloud computing and its benefits for small business owners.
Loops Section Overview
Look below the covers at a subform control , and the form that is inside it. Explore properties and see how easy it is to aggregate, get statistics, and synchronize results for your data. A Microsoft Access subform is used to show relevant calcul…

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question