swiftysw1 Posted July 6, 2015 Posted July 6, 2015 Hi I think we have a problem with our DNS.. When i try to update some our sims workstations; they cant be found.. I then check the IP address through the DNS and its pointing at the wrong ip address.. Our DNS's are stored on two of our 2* DC Servers (MS Server 2008).. Any ideas?
Chuckster Posted July 6, 2015 Posted July 6, 2015 What happens on both servers when you run the command dcdiag /test:dns in command prompt? 1
swiftysw1 Posted July 6, 2015 Author Posted July 6, 2015 What happens on both servers when you run the command dcdiag /test:dns in command prompt? Hi. I have messaged you.. Thanks
Chuckster Posted July 6, 2015 Posted July 6, 2015 Disable IPv6 in your network adapter connection. Simply unchecking the option does this. After disabling IPv6 run the following commands in command prompt in this order... ipconfig /flushdns ipconfig /registerdns Restart the netlogon service or reboot the DCs.
swiftysw1 Posted July 6, 2015 Author Posted July 6, 2015 Disable IPv6 in your network adapter connection. Simply unchecking the option does this. After disabling IPv6 run the following commands in command prompt in this order... ipconfig /flushdns ipconfig /registerdns Restart the netlogon service or reboot the DCs. Ok Done that on Both. But they are still showing old entries in the DNS.
Michael Posted July 6, 2015 Posted July 6, 2015 Please check the IP configuration on each server. I suspect this is the root cause of the problem. You can also (in turn) restart the DNS Server service on each server. Also make sure that each DNS zone - Forward and Reverse can replicate... by default it's not allowed, so you can either allow any server or a specific list of IPs.
Chuckster Posted July 6, 2015 Posted July 6, 2015 Open up DNS Manager --> Right-click the name of one of your affected DCs and then go to the 'Interfaces' tab. There should only be 1 IP address listed of the DC. Make sure it's the same on the other DC. Then, go to servername --> Forward Lookup Zones --> right-click _msdcs.FQDN --> properties. Check that both your DCs are listed in the Name Servers. Do the same again on the other folder which is just your FQDN. Repeat this process on the other server. Usually disabling IPv6 does the trick. Perhaps give it 24 hours before trying something else? BY the way, do you have setup a reverse lookup zone?
Michael Posted July 6, 2015 Posted July 6, 2015 I've never understood why disabling IPv6 does the trick, despite the fact (most likely), you're using an IPv4 range. Microsoft enable IPv6 by default on all modern OSes (Vista and later), so DNS will work with either. You shouldn't need to do anything with IPv6 - as I say, it'll most likely be an IP mis-configuration (on one or both servers) and/or that DNS itself cannot replicate.
Heliosedu Posted September 10, 2015 Posted September 10, 2015 Disable IPv6 in your network adapter connection. Simply unchecking the option does this. After disabling IPv6 run the following commands in command prompt in this order... ipconfig /flushdns ipconfig /registerdns Restart the netlogon service or reboot the DCs. Do you have any idea why this resolves the issue mate?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now