DNG
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2025 03:00 PM
’m setting up a protected web app for DNG. The app is only accessible when users include a specific URL path (e.g., hostname.local/app). If users try to access just the internal server hostname (e.g., hostname.local), they’re redirected to the default IIS landing page.
The challenge is that DNG only allows the internal FQDN (e.g., hostname.local) when configuring the protected web app—it doesn’t let you specify a full URL path.
Is there a workaround or recommended solution to ensure the app is still protected but accessible only through the intended path?
- Labels:
-
Authentication Proxy

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2025 07:19 AM
I think the recommendation would be for you to create a redirect in IIS that forwards someone who accesses the server hostname to the application virtual site/login page.
