Dell PowerConnect W Clearpass 100 Software HP ProCurve MSM Integration Guide - Page 18

Step 4 - DNS Proxy & Interception configuration

Get Dell PowerConnect W Clearpass 100 Software PDF manuals and user guides View all Dell PowerConnect W Clearpass 100 Software manuals
Add to My Manuals
Save this manual to your list of manuals

Page 18 highlights

Step 4 - DNS Proxy & Interception configuration In order for the MSM to be able to intercept and redirect any new Guest users to the amigopod hosted Web Login page, the controller must get involved in the DNS resolution process of these users. The MSM DNS configuration allows the definition of upstream DNS servers along with the enablement of DNS Proxy & DNS Interception required to perform these redirects as shown in the screen capture below: Without the DNS Proxy feature enabled attempts by Guest users to resolve globally unknown hosts and domain names typically used in corporate Intranet environments would fail. This DNS resolution failure would lead to the Guest user's browser never attempting a HTTP transaction and hence the MSM would not be able to redirect the client's session to the amigopod Web Login page. Based on this you can see the DNS configuration is a critical component in the successful user experience for Guest access. CONFIDENTIAL 18

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
CONFIDENTIAL
18
Step 4 – DNS Proxy & Interception configuration
In order for the MSM to be able to intercept and redirect any new Guest users to the amigopod
hosted Web Login page, the controller must get involved in the DNS resolution process of these
users. The MSM DNS configuration allows the definition of upstream DNS servers along with
the enablement of
DNS Proxy
&
DNS Interception
required to perform these redirects as shown
in the screen capture below:
Without the
DNS Proxy
feature enabled attempts by Guest users to resolve globally unknown
hosts and domain names typically used in corporate Intranet environments would fail. This DNS
resolution failure would lead to the Guest user’s browser never attempting a HTTP transaction
and hence the MSM would not be able to redirect the client’s session to the amigopod Web
Login page.
Based on this you can see the DNS configuration is a critical component in the successful user
experience for Guest access.