Planning for Domain Name System Updates
Planning for Domain Name System Updates
To allow users to locate your web tier and optional load balancer, you must buy publicly resolvable names for these systems. Do the following:
Define a domain name, for example, mydomain.com
Define host names, for example, myhost.mydomain.com
Contact a Domain Name registrar, and register the domain name and associated host names.
Clients using Self-Service and risk-based authentication (RBA) must be able to resolve to the virtual host name using Domain Name System (DNS).
If your deployment has a load balancer, the virtual hostname must resolve to the public IP address of the load balancer.
If your deployment does not have a load balancer, the virtual hostname must resolve to the public IP addresses of each web tier.
Related Articles
Cloud Access Service - Planning Access Policies 13Number of Views Cloud Access Service - Planning Your Identity Router Deployment 20Number of Views HTTP Federation Proxy Planning Worksheet 13Number of Views Planning to Add an Application Using HTTP Federation Proxy 18Number of Views Deployment Planning Checklist 102Number of Views
Trending Articles
RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows Configuring a Checkpoint firewall to work with SecurID RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Patch Updates Unable to login to RSA Authentication Manager Security Console as super admin
Don't see what you're looking for?