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 192.168.100.1
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
_msdcs.TRYSUPPLY.local
&
TRYSUPPLY.Local
Both zones had sub folders under each one
When I run DCDIAG /fix I get some errors i.e. _ldap._tcp.pdc._msdcs.TRYS
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.
Who is Participating?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
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...
Capture1.JPG
Capture2.JPG
Capture3.JPG
Capture4.JPG
Three was critical - and good, you're set good.
Four was interesting and quite possibly why you're experiencing problems.
Try this (from: http://evansblog.thebarrs.info/2013/02/windows-server-force-your-network.html )
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
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.
Experts Exchange Solution brought to you by
All you had to do was restart to get the netlogon service to register DNS info.
Next, I'd have to ask WHY move TO a 192.168.1 address - that's the standard one that all home class routers use - if you ever try using VPN, you could now have a LOT of problems. You were much better off sticking with .100
If you can undo what you did, I would recommend it.
If not, be aware of the complications you've now introduced if/when you have issues in the future.
Confirm your DNS settings are correct in DHCP (handing out the IP of the DC as the ONLY DNS server), confirm the TCP/IP properties of the server point ONLY to itself for DNS (no google/isp dns servers. IDEALLY, post your settings in screen shots from the server and a workstation so we can see and confirm you are correct...