DNS - Server 2012
Info
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.
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.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I don't know who told you to uninstall and reinstall DNS and DHCP - that was a waste of time that might just have caused you problems.
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...
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...
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...
Capture1.JPG
Capture2.JPG
Capture3.JPG
Capture4.JPG
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
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: 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.
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.
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.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial