Hi All,
We are migrating a Navision/SQL server to some new boxes, however we have many hard coded references to their A records in DNS. The issue is here of course that when we cut over to the new servers, all those applications will be looking at the OLD servers and this is very much not a good thing. Of course if we had pointed everything to a CNAME then we wouldn't have had this problem, but I digress.
So I was thinking I could do the following:
1. Stop the servers from registering themselves in DNS.
2.Delete the A records of both these servers.
3. Create a new A record as a different name.
4. Use the old A record FQDN's as a CNAME on the new A records.
This means we could simply cut over by deleting the CNAME and adding it to the new server's A records. This when our applications do a lookup on the old A records it will resolve to the new servers.
The problem is though that we still need those old servers to be up and running post migration. I know that AD relies heavily on DNS, so am I able to delete a server's A record and create a new record and have everything still work? Or will things like logging in/group policy/whatever break?
Any help is really appreciated.