Cheers Ken. What happens to the URL the user seen going forward in this case? The friendly URL or serverA/serverB?
On Wed, 25 Sep 2019 at 21:12, Ken Schaefer <[email protected]> wrote: > You do this in DNS > > > > You’d have records for: > > ServerA -> IP address > > ServerB -> IP address > > Already, so that browsers can find ServerA and ServerB. > > > > In the same DNS zone (if you are using AD at work, then you already most > likely have Microsoft DNS running to support that AD domain), create a > CNAME record that points “myapp” -> A record for ServerA or ServerB. > > CNAME is effectively an alias record that points to another record > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Tom P > *Sent:* Friday, 20 September 2019 3:05 PM > *To:* ozDotNet <[email protected]> > *Subject:* Friendly URL for intranet apps > > > > Hi folks > > > > I’m moving an intranet app from an old server to a new server. Currently > the users access the site with a URL like http://*serverA*/appName/ > <http://serverA/appName/>. > > > > The issue is now that I’m moving the app the server name in the URL will > change to http://*serverB*/appName <http://serverB/appName>. > > > > All the users are forced to update their bookmarks which is a bit lame in > my view. > > > > I’m sure this isn’t a new issue. What is a good way to handle this? > > > > Would be good to have a URL like http://myapp.mydomain.com.au but where > would this be set up? In IIS somewhere? DNS entry? How and where to set it > up? > > > > Cheers > > -- > > Thanks > > Tom > -- Thanks Tom
