Link to home
Start Free TrialLog in
Avatar of Travis Hahn
Travis HahnFlag for United States of America

asked on

DNS - Server 2012


Server 2012 - Single Server that is DNS DHCP File Print server (10 users), it is the Gateway with Cox Cable Business no static outside IP.

IP was

Domain is TRYSUPPLY.LOCAL (fake name for example)

The company moved and the new IP Scheme was set on new Firewall as 192.168.1.x  (Changed the NIC info)

I uninstalled DNS/DHCP - reinstalled DNS/DHCP with new IP info

Now my users have slowness issues.

My DNS manager has 2 Forward Lookup Zones




Both zones had sub folders under each one

When I run DCDIAG /fix I get some errors i.e. _ldap._tcp.pdc._msdcs.TRYSUPPLY.Local timed out after none of the configured DNS servers responded

I think that the DNS/DHCP uninstall/reinstall did not completely remove the old info and I am having DNS issues, however I am not sure what to do to fix.
Avatar of Lee W, MVP
Lee W, MVP
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Travis Hahn


So I cannot undo what I did - my hand was dealt after the consultant didnt run his config by us, and had setup everything first.

I have attached screen shots - i didnt black everything out - to time consuming.

The one thing I did notice is that my Domain/Network Profile is set to public...
Ok, pictures one and two are unimportant - I can delete them for you if you can't.

Three was critical - and good, you're set good.

Four was interesting and quite possibly why you're experiencing problems.

Try this (from: )
    Go to Network Connections (from the Network and Sharing Center, click on "Change adapter settings".)

    Go to the properties of one network connection marked as "Unidentified" but on the private LAN.

    Go to the properties for IPv4.

    Click the "Advanced..." button.

    Select the DNS tab.

    Enter your domain name into the text box for "DNS suffix for this connection:".

    Disable and then enable the connection to get NLA to re-identify the location.
And my apologies if I was harsh or blunt without warning.  I see a LOT of instances, online and with clients where people don't know what they are doing and mess things up significantly.  If your consultant did a bad job, then get a second opinion (like a mechanic) or post to forums before jumping right in.  For everything that gets made simpler with a new version of Windows, two more things get introduced and more complicated.  If you don't have the experience to handle them, you're just likely to cause worse problems.