Re: Friendly URL for intranet apps

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 wrote: > You do this in DNS > > > > You’d have records for: > > ServerA -> IP address > > ServerB -> IP address > > Already, so that

RE: Friendly URL for intranet apps

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

Re: Friendly URL for intranet apps

Hi, Also check to see if the web server, iis or other, is accepting All ips or named Ips. you might have to add http://servera to the list of bindings. Davy. David JONES djones...@gmail.com +33 7 66 42 54 07 +33 6 52 03 96 70

Re: Friendly URL for intranet apps

Cheers. Will speak to the admin about setting this up. On Fri, 20 Sep 2019 at 15:13, DotNet Dude wrote: > An A or CNAME dns record can do what you want > > On Fri, 20 Sep 2019 at 15:04, Tom P wrote: > >> Hi folks >> >> I’m moving an intranet app from an old server to a new server. Currently >>

Re: Friendly URL for intranet apps

An A or CNAME dns record can do what you want On Fri, 20 Sep 2019 at 15:04, Tom P wrote: > 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/. > > The issue is now that I’m moving the app