# A wrinkle in time: A case study in DNS poisoning

**Authors:** Harel Berger, Amit Z. Dvir, Moti Geva

arXiv: 1906.10928 · 2019-06-27

## TL;DR

This paper introduces a novel DNS poisoning detection method based on response time analysis, validated across various environments, achieving over 99% detection accuracy without protocol modifications.

## Contribution

The authors present a new timing-based DNS poisoning detection technique and a validation system that works without altering existing DNS infrastructure.

## Key findings

- High detection accuracy exceeding 99%
- Effective across LAN, cloud, and ISP environments
- Does not require DNS protocol changes

## Abstract

The Domain Name System (DNS) provides a translation between readable domain names and IP addresses. The DNS is a key infrastructure component of the Internet and a prime target for a variety of attacks. One of the most significant threat to the DNS's wellbeing is a DNS poisoning attack, in which the DNS responses are maliciously replaced, or poisoned, by an attacker. To identify this kind of attack, we start by an analysis of different kinds of response times. We present an analysis of typical and atypical response times, while differentiating between the different levels of DNS servers' response times, from root servers down to internal caching servers. We successfully identify empirical DNS poisoning attacks based on a novel method for DNS response timing analysis. We then present a system we developed to validate our technique that does not require any changes to the DNS protocol or any existing network equipment. Our validation system tested data from different architectures including LAN and cloud environments and real data from an Internet Service Provider (ISP). Our method and system differ from most other DNS poisoning detection methods and achieved high detection rates exceeding 99%. These findings suggest that when used in conjunction with other methods, they can considerably enhance the accuracy of these methods.

## Full text

_Full body text omitted from this summary view._ Fetch the complete paper as Markdown: https://tomesphere.com/paper/1906.10928/full.md

## Figures

29 figures with captions in the complete paper: https://tomesphere.com/paper/1906.10928/full.md

## References

51 references — full list in the complete paper: https://tomesphere.com/paper/1906.10928/full.md

---
Source: https://tomesphere.com/paper/1906.10928