SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a web app on a SharePoint 2010 farm, that we use for our internal intranet example “”

We would like to build a 2013 farm, but pilot its development in the early stages so that we can learn from a gradual shift over of teams and content, instead of all at once. I know it may seem like a lot of extra work moving content over in this way, instead of attaching the 2010 database to the new farm, but there is a lot of orphaned content that we would like to leave on the old farm database and we hope to start fresh with a new one.

With that said we would like to keep both 2010 and 2013 running, am I incorrect in my understanding that if my 2010 farm is using a web app with the address “”, that I cannot use this for any 2013 web app I create as it would create a conflict in DNS?

If i am correct in that understanding, my concern is that we would eventually be migrating users and traffic away from the old web app “” in 2010 as it would now be going to the 2013 farm instead. So am I forced to abandon the 2010 farm address of “” once it is no longer needed and have people start using a new address for the 2013 farm of, for example, “”?

Is it possible that i would be able to replace the 2013 address with the 2010 web app address, once it is no longer being used? Is this something I have to configure in the web app or is there some DNS trickery? Any issues with attempting this type of operation in general?

share|improve this question

For the most part, John is correct. However, if you have some hardware handling your DNS, such as an F5 box, it is possible to create rules there that will route requests to one farm or another based on the site URL being requested. For example, a rule could be created that would route all // to 2013 while requests to // could be directed to your 2010 farm.

We did this for our 2007 to 2010 migration and it worked well. The only catch was that we had to point // to the newer farm so that it could properly serve supporting files, like CSS and Javascript.

share|improve this answer

While your 2010 farm is using, your 2013 farm cannot use it. While both are running, your 2013 farm would need a new address.

Once you decommission your 2010 farm, however, you can assign the 2010 DNS entry to your 2013 farm and configure an Alternate Access Mapping to accept that DNS alias.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.