KB40984: How to disable DNS lookup on MicroStrategy Web

INTRODUCTION
Strategy Web does a DNS lookup against the client IP to get the machine client name. This information is sent to the Strategy Intelligence Server to record data for Strategy Enterprise Manager logging. This allows Strategy Enterprise Manager users to create and run reports based on the statistics gathered per client machine. The motivation behind a DNS lookup is that often times, the IP addresses do not remain constant for a given client machine, but the client machine name does. This makes it easier to report based on the client machine name than on the client machine IP. 
Sometimes the DNS lookup is slow, increasing the time it takes to log into a project through Strategy Web. In these cases, administrators may disable the lookup to improve the login time. Administrators can also disable the lookup temporarily as a troubleshooting step to determine if DNS lookup is a bottleneck in the login workflow.
 
DISABLING DNS LOOKUP 
For web servers on Windows/IIS, DNS lookup can be disabled by following the steps below:

1. Open the registry, and make a backup.
2. Navigate to HKEY_LOCAL_MACHINE > Software > Wow6432Node (if on a 64-bit machine) > Strategy > JNI Bridge > Configuration > JVM Options
3. Add the following value to the Web Options key: -Dmstr.clientNameLookup=false;
4. Navigate to HKEY_LOCAL_MACHINE > Software > Wow6432Node (if on 64bit machine) > Strategy > JNI Bridge 64 > Configuration > JVM Options
5. Add the following value (same as above) to the Web Options key: -Dmstr.clientNameLookup=false;
6. Restart IIS

For all other web servers in universal environments, the syntax will be the same, however instead of modifying the registry, modify the Java Options. The specific file to modify will depend on the particular application server. The web server must be restarted for the change to take effect. Contact the web server administrator for more details on where this change should be made.
 
VERIFYING THAT DNS LOOKUP IS DISABLED
Administratos can verify that DNS lookup is disabled by reviewing a Kernel XML API trace that captures a login event. At the time of login, an entry will be logged to indicate the successful creation of a session. See the example below.

2012-08-29 12:17:43.350-05:00 XML CreateSession Successful: User administrator, Project 0

The entry immediately before this line will indicate whether DNS lookup has been disabled or not. If DNS lookup is not disabled, the client machine name will be visible - see the bolded section in the example below.

2012-08-29 12:13:21.305-05:00 XML Command: <st><sst><st><cmd><crs ln="administrator" pwd="" npwd="" pgd="B19DEDCC11D4E0EFC000EB9495D0F44F" clid="Server Machine: 10.22.0.161 Client Machine: 10.22.0.161" clmn=" Client Machine Name: machine.domain.com" amd="1" snf="0" rws="10" sws="1" clt="6"><reg_opt lcl_rsl="1"><reg_md lcl_id="1033" lcl_rsl="1"/><reg_dt lcl_id="1033" lcl_rsl="1"/><reg_int lcl_id="1033" lcl_rsl="1"/><reg_msg lcl_id="1033" lcl_rsl="1"/><reg_num lcl_id="1033" lcl_rsl="1"/></reg_opt></crs></cmd></st></sst></st>

On the other hand, if DNS lookup is disabled, the client machine will not be visible - see the bolded section in the example below.

2012-08-29 12:17:43.211-05:00 XML Command: <st><sst><st><cmd><crs ln="administrator" pwd="" npwd="" pgd="B19DEDCC11D4E0EFC000EB9495D0F44F" clid="Server Machine: 10.22.0.161 Client Machine: 10.22.0.161" clmn=" Client Machine Name:  " amd="1" snf="0" rws="10" sws="1" clt="6"><reg_opt lcl_rsl="1"><reg_md lcl_id="1033" lcl_rsl="1"/><reg_dt lcl_id="1033" lcl_rsl="1"/><reg_int lcl_id="1033" lcl_rsl="1"/><reg_msg lcl_id="1033" lcl_rsl="1"/><reg_num lcl_id="1033" lcl_rsl="1"/></reg_opt></crs></cmd></st></sst></st>