From the course: Windows Server 2016: Active Directory Federation Services

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Internal and external FQDNs

Internal and external FQDNs - Windows Server Tutorial

From the course: Windows Server 2016: Active Directory Federation Services

Start my 1-month free trial

Internal and external FQDNs

- When publishing an application or website in the Web Application Proxy, you're asked to give two URLs. An external URL, and a back-end, or internal URL. In the last demonstration, we used the same URL for both, which is one way to do it. And there's an argument that this may be the easiest way, but let's take a couple minutes to look at these two URLs and their individual requirements. First, let's take a look at the back-end URL. This is the URL of the app or website on the intranet. This is the address that anyone on the internal network would type in to access the application. For that URL to work, the web server has to have a certificate with exactly that name. But let's say our Active Directory domain is separate from our web presence. Let's take a look at this scenario. If the internet domain is landonhotel.local, then the web server might have an address of iis01.landonhotel.local. Let's say we have an HR application on that web server for employees to check and request paid…

Contents