# dns\_query\_time\_query\_time

**URL:** <https://community.netdata.cloud/t/dns-query-time-query-time/2593>\
**Category:** Alerts\
**Created:** [February 21, 2022, 4:28pm UTC](https://community.netdata.cloud/t/dns-query-time-query-time/2593 "2022-02-21T16:28:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ancairon](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ancairon/32/1001_2.png) [@Ancairon](https://community.netdata.cloud/u/Ancairon)\
**Post date:** [February 21, 2022, 4:28pm UTC](https://community.netdata.cloud/t/dns-query-time-query-time/2593/1 "2022-02-21T16:28:39Z")

</div>

# dns\_query\_time\_query\_time

## DNS

This alert presents the average DNS query round trip time (RTT) over the last 10 seconds.

If the DNS query exceeds a time limit to complete its operation (aka if it times out), then the alert is raised into warning.

> **What is Round Trip Time?**
>
> > In networking, round-trip time (RTT), also known as round-trip delay time (RTD) is defined as  
> > a metric that measures in milliseconds the amount of time it takes for a data packet to be  
> > sent plus the amount of time it takes for acknowledgement of that signal to be received. This  
> > time delay includes propagation times for the paths between the two communication endpoints.[1](https://www.stormit.cloud/post/what-is-round-trip-time-rtt-meaning-calculation)

> **What is the main cause of DNS Latency?**
>
> - Cache misses  
> Even if a resolver can provide very good cache hit latency, cache misses are unavoidable and are  
> very costly in terms of latency.
> 
> - DNS Server Location
> 
> - Wireless networks
> 
> - Malicious DNS Traffic
> 
> - Under-scaling of DNS Server

For further information, please refer to our _References and Sources_ section.

> **References and Sources**
>
> 1. [What is Round-Trip Time (RTT)?](https://www.stormit.cloud/post/what-is-round-trip-time-rtt-meaning-calculation)
> 2. [Causes and mitigations of DNS latency](https://developers.google.com/speed/public-dns/docs/performance#introduction_causes_and_mitigations_of_dns_latency)
> 3. [What is DNS Latency and Why Should You Care?](https://www.smartdnsproxy.com/news/smart-dns-proxy/what-is-dns-latency-and-why-should-you-care-158.aspx)
> 4. [Configure your network settings to use Google Public DNS](https://developers.google.com/speed/public-dns/docs/using)

### Troubleshooting Section

This alert can have multiple causes.

As a first step, you can try changing your DNS server. Your current configuration might be using a  
slow server, or what your ISP provides might not be the best. You can find more information on  
[Google Developers](https://developers.google.com/speed/public-dns/docs/using) on how to configure your settings for your specific OS to use Google’s Public DNS.