Name Resolutions - OS Test
To ensure reliable and fast name resolution on physical desktops, it is essential to monitor DNS availability and response time. If the DNS server is unavailable, the system cannot resolve hostnames, leading to application and network access failures. Slow DNS response times can delay login processes, app launches, and website loading. Proactive monitoring helps detect and fix DNS issues before they impact user productivity.
This test emulates a client accessing DNS to issue a query. The query can either request DNS to resolve a domain name to an IP address or vice versa. Based on the response reported by the server, measurements are made of the availability and responsiveness of the DNS component of the physical desktop group.
Target of the test :A Physical Desktop Group
Agent deploying the test : A remote agent
Outputs of the test: One set of results will be reported for every physical desktop.
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The nick name of the Physical Desktop Group component for which this test is to be configured. |
|
Port |
The port at which the specified Host listens. By default, this is NULL. |
|
Report Powered OS |
This flag is relevant only for those tests that are mapped to the Physical Desktops Details layer. If this flag is set to Yes (which is the default setting), then the 'inside view' tests will report measures for even those physical desktops that do not have any users logged in currently. Such desktops will be identified by their name and not by the username_on_physicalmachinename. On the other hand, if this flag is set to No, then this test will not report measures for those physical desktops to which no users are logged in currently. |
|
Report By User |
This flag is set to Yes by default. This implies that the physical machines in environments will always be identified using the login name of the user. In other words, this test will, by default, report measures for every username_on_physicalmachinename. |
| Measurement | Description | Measurement Unit | Interpretation | ||||||
|---|---|---|---|---|---|---|---|---|---|
|
DNS availability |
Indicates whether a successful response is received from the DNS server in response to the emulated user request. |
Percent |
An availability problem can be caused by different factors – e.g., the server process may not be up, a network problem may exist, or there could be a configuration problem with DNS. |
||||||
|
DNS response time |
Indicates the time taken by DNS server to respond to a request. |
Seconds |
An increase in response time can be caused by several factors such as a server bottleneck, a configuration problem with DNS, a network problem, etc. |
||||||
|
Is hosts file modified recently? |
Indicates whether or not the hosts file has been modified recently. |
|
The values that this measure can report and its corresponding numeric equivalents are listed in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate whether the host file was modified. In the graph of this measure however, the same is represented using the corresponding numeric equivalents only. If the value of this measure is Yes, then use the detailed diagnosis to find the modification. |