Having some DNS problems with Server 2012


  • A couple years ago I was hired to administer a location with a network of about 50 computers and three servers.  One is a Exchange server/DNS,  one is a file server/dhcp and one linked to financial software.   This whole network was kinda finagled over the past 20 years by a few guys and i'm on the tail end of it.   Network principles are probably where I need to focus the most of my brushing up,  but I generally do alright,  generally my job is mostly troubleshooting computer issues.

    Well,  about six months ago we started having problems with DNS resolution.   All the computer have a reference to the exchange/DNS server as their primary DNS(if the IP of the exchange server isn't the first DNS reference outlook won't connect to the exchange server,  I learned)   We have a few outlying areas that are using VPNs to connect to the file server and exchange server.  Before this started we had some problems with the VPNs losing connectivity and my boss wanted me to make is so that the outlying centers could still access the internet on their web browsers if the VPN was down so I added secondary and tertiary DNS servers in the form of ISP provided DNS addresses.   This worked,   but shortly afterwards we started having DNS problems... so I took out all the outside DNS references,  thinking maybe that had caused the problem,  but it didn't resolve the problem.

    So what's happening is that frequently i'll try to bring up web sites and it'll sit at "resolving host" for a while,  then i'll get an error like "DNS_PROBE_FINISHED_BAD_CONFIG" "  or "ERR_NAME_NOT_RESOLVED"     but then the page will either come up shortly after giving me that error,  or if i press the "refresh" button the web site will appear.      I've been messing with "forwarders" and "root hints" on the DNS server to try to resolve this,  but nothing has improved.  

    If anyone has any flashes of insight i'd appreciate it.

    Monday, July 9, 2018 9:34 PM

All replies

  • Domain controller and all members should have the static address of DC listed for DNS and no others such as router or public DNS. Posing an unedited ipconfig /all of DC and problem client may help.



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, July 10, 2018 12:02 AM
  • Hi,

    Thanks for your question.

    • Use the nslookup command to resolve the address of the DNS server. If it is unsuccessful, it is unable to access the DNS server. If successful, continue to resolve the website address.
    • Clean up DNS cache records.Use the ipconfig/flushdns command to clean up the DNS cache before you visit the website.
    • Set the forwarder of the DNS server to the DNS address provided by the ISP.

    Best regards,


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Tuesday, July 10, 2018 2:34 AM
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

    If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Friday, July 13, 2018 3:14 AM