> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/denial-of-service/dnsreflection.md).

# dnsreflection

Explanation The dnsreflection event is detection within the Netography Fusion Portal that detects DNS reflection attacks. These types of attacks use DNS servers to amplify the size of the incoming tra

**Explanation**

The dnsreflection event is detection within the Netography Fusion Portal that detects DNS reflection attacks. These types of attacks use DNS servers to amplify the size of the incoming traffic to a victim's website by spoofing the source IP addresses of the requests. This can lead to denial of service (DoS) attacks as the victim's server is overwhelmed with traffic.

**What to Look For**

In order to examine the results of the dnsreflection event, users should review the network traffic logs. Specifically, they should look for a high volume of DNS requests originating from multiple source IP addresses. In addition, this traffic may also be characterized by unusually large query sizes or traffic volumes. At the endpoint level, users should monitor for any signs of unusual CPU or memory spikes, as this may indicate that the device is being used in a reflection attack.

**Related MITRE ATT\&CK Categories**

[Impact: Network Denial of Service, Technique T1498 - Enterprise](https://attack.mitre.org/techniques/T1498)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fusion.vectra.ai/detection-models/library/denial-of-service/dnsreflection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
