BACKGROUND
Strategy connectivity functionality relies on successful DNS resolution of the source and target machines in order to operate correctly. If there is an issue with the DNS resolution such as host names not resolving to the correct IP addresses or vice versa, errors, connection failure, or unexpected behavior may result.
Some common scenarios where DNS resolution issues can cause problems with Strategy software include:
- Connecting Strategy Web to the Strategy Intelligence Server
- Configuring the Strategy Intelligence Server to use Integrated Authentication for user login
- Configuring the Strategy Intelligence Server to connect to a data source using Kerberos
- Connecting to the Strategy Intelligence Server using Strategy Command Manager or Health Center
- Capturing usage statistics on the Strategy Intelligence Server
This Knowledge Base article outlines a procedure for testing the DNS resolution between two machines using the nslookup utility to verify that it is working correctly on Windows or Linux operating systems.
On Windows:
Open a command prompt as administrator, then run the following (hostname is used here as a placeholder for the actual hostname to be tested):
nslookup hostname
Results should be in the format:
Server: domaincontroller.yourdomain.com
Address: 10.x.y.z
Name: hostname.yourdomain.com
Address: 10.a.b.c
Ensure that 10.a.b.c is the correct IP address for the hostname tested. If it is not, then there is a DNS issue that is preventing the hostname's IP address from being correctly resolved.
Next, run this:
nslookup 10.a.b.c
(where 10.a.b.c is the IP address that was returned by the previous nslookup command)
The results should be the same as the first query:
Server: domaincontroller.yourdomain.com
Address: 10.x.y.z
Name: hostname.yourdomain.com
Address: 10.a.b.c
Ensure that the hostname returned here is the correct hostname for the IP address being tested (it should match the original hostname tested). If it is not, then there is a DNS issue that is preventing the IP address correctly resolving to the hostname.
On Linux: Run the following at a terminal prompt (
hostname is used here as a placeholder for the actual hostname to be tested):
# nslookup hostname
Results should be in the format:
Server: 10.x.y.z
Address: 10.x.y.z#53
Name: hostname
Address: 10.a.b.c
Ensure that 10.a.b.c is the correct IP address for the hostname tested. If it is not, then there is a DNS issue that is preventing the hostname's IP address from being correctly resolved.
Next, run this:
# nslookup 10.a.b.c
(where 10.a.b.c is the IP address that was returned by the previous nslookup command)
Results should be in the format:
Server: 10.x.y.z
Address: 10.x.y.z#53
c.b.a.10.in-addr.arpa name = hostname.
Ensure that the hostname returned here is the correct hostname for the IP address being tested (it should match the original hostname tested). If it is not, then there is a DNS issue that is preventing the IP address correctly resolving to the hostname.
ACTIONIf any of the DNS resolution tests above fail, contact the system or network administrator and provide the results of the tests so they can correct the system or network issue.
