Domain Name Server (DNS) task

Example data for the DNS tasks, and information about how to interpret the data.

Task, Type, Requests, Busy %,  CPU used, CPU %, "avg CPU", "avg ET",  longest,       date,            time
    ,     ,         ,       ,   Seconds,      ,  uSeconds, uSeconds, uSeconds,           ,
   0,  DNS,    14002,    0.0,  0.122578,   0.0,         9,       11,      463, 2014/03/18, 12:56:33.987671
Summ,  DNS,    14002,    0.0,  0.122578,   0.0,         9,       11,      463, 2014/03/18, 12:56:33.987671

The CHINIT uses a single DNS task. The example shows that the task processed 14002 requests and on average the request used 9 microseconds of CPU and took 11 microseconds of elapsed time.

The longest DNS request took 463 microseconds elapsed time, and this occurred at 12:56:33 local time.

The fields are calculated from:

• Duration: qwhs.qwhsdurn
• Requests : qctreqn
• Busy %: qcteltm and duration
• CPU used: qctcptm
• CPU %: qctcptm and duration
• Average CPU: qctcptm and qctreqn
• Average ET: qcteltm and qctreqn
• Longest: qctlgdu
• Longest at: qctlgtm

The DNS task can go out of your enterprise to look up the IP address associated with a name. If the average Elapsed time is significantly more than the average CPU time used, you might have some long requests.

If the value of the longest request time is unacceptable you should work with your network team to investigate why you are having long requests. It might be that we have an invalid name in your connections.

If the DNS task is busy for 25% of the duration, consider investigating the cause further.

Note: There are requests to the DNS task that are not DNS lookups, so you might have the number of requests being greater than zero - but no longest request information.