Mark Litin
asked on
Verifieing DNS settings after Domain Migration
Hi , and thanks for any guidance you may have.
I have a client for whom I am replacing their current server serving the domain Hanson.local with a server with Windows server 2012 Essentials, serving the same domain Hanson.local. The servers were never going to the be running at the same time, but alas, they will be running parallel for a time. So I migrated the domain of the new server to Hanson1.local using these instructions:
https://mizitechinfo.wordpress.com/2013/06/10/simple-guide-how-to-rename-domain-name-in-windows-server-2012/
I observe now that clients connecting to the domain get slowly resolved DNS (failure to connect, then slow to connect). The clients having these problems are using the server IP as the DNS (192.168.256.10)
All client computers were able to connect to the new domain and access the resources on that server without a problem.
I looked into the DNS setting on the server, and noticed that within the forward lookup settings, both old and new domains are referenced I;m concerned the migration is not complete that there is possible cleanup I need to to to make setup the domain completely and correctly.
I have a attached 5 snips of the DNS setup and the network setup of the server.
I would like to ensure the DNS is setup correctly on the new server and remove all references to the old domain if necessary,
Any assist in this regard with be most welcome.
Thank you kindly.
Mark
hanson.PNG
hanson1.PNG
hansonserver.PNG
dot10.png
dot11.PNG
I have a client for whom I am replacing their current server serving the domain Hanson.local with a server with Windows server 2012 Essentials, serving the same domain Hanson.local. The servers were never going to the be running at the same time, but alas, they will be running parallel for a time. So I migrated the domain of the new server to Hanson1.local using these instructions:
https://mizitechinfo.wordpress.com/2013/06/10/simple-guide-how-to-rename-domain-name-in-windows-server-2012/
I observe now that clients connecting to the domain get slowly resolved DNS (failure to connect, then slow to connect). The clients having these problems are using the server IP as the DNS (192.168.256.10)
All client computers were able to connect to the new domain and access the resources on that server without a problem.
I looked into the DNS setting on the server, and noticed that within the forward lookup settings, both old and new domains are referenced I;m concerned the migration is not complete that there is possible cleanup I need to to to make setup the domain completely and correctly.
I have a attached 5 snips of the DNS setup and the network setup of the server.
I would like to ensure the DNS is setup correctly on the new server and remove all references to the old domain if necessary,
Any assist in this regard with be most welcome.
Thank you kindly.
Mark
hanson.PNG
hanson1.PNG
hansonserver.PNG
dot10.png
dot11.PNG
ASKER
Hi
I changed it because the plans changed from completely replacing the old server and replicating the domain to the new server to running them in parallel for a time, therefore having two servers presenting the same domain, which would be problematic.
I changed it because the plans changed from completely replacing the old server and replicating the domain to the new server to running them in parallel for a time, therefore having two servers presenting the same domain, which would be problematic.
Is the old server running some version of SBS or Essentials?
ASKER
Hi DrDave242
the old server is running server 2000 the new is Server 2012 Essentials.
Thanks
Mark
the old server is running server 2000 the new is Server 2012 Essentials.
Thanks
Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi DrDave242
Well, that's a real eye opener, and II'm a bit shocked. But that is what it is.
Server 2000 is not SBS.
I'll have to decide whether I'm going to rebuild this server or run with it as is. The demands to be placed on the server will be minimal, and the functions seem without issue, and clients relationship with the server seem normal and without issue.
So theoretically, with Server 2012 standard, after using the process I used to update the domain, would you expect the DNS listings i provided to be the same?
Thanks for the the enlightenment. I'm more informed and somewhat chagrined.
Mark
Well, that's a real eye opener, and II'm a bit shocked. But that is what it is.
Server 2000 is not SBS.
I'll have to decide whether I'm going to rebuild this server or run with it as is. The demands to be placed on the server will be minimal, and the functions seem without issue, and clients relationship with the server seem normal and without issue.
So theoretically, with Server 2012 standard, after using the process I used to update the domain, would you expect the DNS listings i provided to be the same?
Thanks for the the enlightenment. I'm more informed and somewhat chagrined.
Mark
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, DrDave242
I appreciate all the clarity.
Mark
I appreciate all the clarity.
Mark