What is DNS?

Humans type names; networks need numbers.

The Domain Name System translates hostnames like www.example.com into IP addresses. It runs primarily on UDP port 53 and is a frequent DDoS target and amplification vector.

How a lookup works

Your device asks a recursive resolver (often your ISP or 1.1.1.1). The resolver queries root, TLD and authoritative nameservers until it gets an answer.

Results are cached with TTL values to reduce load. Stale caches during attacks can prolong outages if TTLs are too high.

Common record types

A / AAAA - IPv4 and IPv6 addresses. MX - mail servers. NS - authoritative nameservers. CNAME - alias to another name. TXT - verification and SPF.

Anycast DNS spreads queries across PoPs - useful for resilience but requires DDoS capacity at each edge.

A DNS lookup, left to right

  1. 01

    Your device

    Requests the IP address for a hostname from a recursive resolver.

  2. 02

    Resolver

    Checks its cache, then queries root and TLD servers if needed.

  3. 03

    Authoritative DNS

    Returns the record; the resolver caches it and sends the answer back.

DNS and DDoS

DNS amplification sends small queries that trigger large responses from open resolvers, spoofing the victim's IP as source.

Mitigation: close open resolvers, rate-limit port 53, use DNSSEC-aware filters and anycast with sufficient scrubbing capacity.

DNS amplification, packet to impact

  1. 01

    Spoofed query

    The attacker sends small UDP queries to open resolvers with the victim's IP forged as the source.

  2. 02

    Amplified replies

    Resolvers send much larger DNS responses toward the victim, multiplying inbound traffic.

  3. 03

    Scrub and deliver

    Edge filters identify abnormal DNS response patterns, drop attack packets and pass valid service traffic.

UDP flood

A UDP flood sends a high rate of packets at a service or network. Because UDP does not require a handshake, the destination may spend resources processing traffic that has no valid application session behind it.

TMW Shield compares incoming UDP traffic with the protected service profile. Protocol-aware filters discard malformed, unexpected or abnormal-rate packets at the edge while allowing traffic that matches the service to continue.

UDP flood, from packet to impact

  1. 01

    Packet flood

    Distributed sources send large volumes of UDP packets to a target IP and port.

  2. 02

    Service pressure

    Unexpected or malformed packets consume bandwidth and packet-processing capacity.

  3. 03

    Filter at the edge

    TMW Shield applies protocol and rate-aware rules, drops attack traffic upstream and passes valid service packets.

DNS FAQ

  • UDP is fast for small queries. Large responses may fall back to TCP. Attackers abuse UDP because it is stateless.

Protect authoritative and recursive DNS

TMW Shield filters DNS floods and amplification with protocol-aware UDP profiles.