The NLS is one of the most important things in the URA configuration because it's what allows URA clients to detect that they are connected to the corporate network when they are in the office. If they cannot connect to the NLS, they will assume that they are still on the public internet and try to establish the URA connection, and that's not a very good idea while inside the office, just like you wouldn't want people to use their VPN connection in that situation.
The NLS is simply a web server that listens for HTTPS requests and replies to them. It does not need to contain any specific content, so a blank site is perfectly fine. Essentially, you can use any internal web server for that role, but the URA Getting Started Wizard assumes you want to keep things simple and uses itself for it.
The automatic setup chooses a distinct name to represent this role, as it cannot be the same name used by URA clients to access it. The reason for this is that since the URA clients...