Timeout - Do Not Respond

The module is designed to prevent any response from being sent, effectively leading to a connection timeout.

In both UDP and TCP modes, the client/resolver will receive nothing at all.

Format

timeout.yourdomain.com

This module has no parameters.

Examples

In the default (UDP) mode, we can see that the client is unable to receive any response, resulting in a timeout. The client makes three attempts:

# dig timeout.yourdomain.com @127.0.0.1

;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out

; <<>> DiG 9.18.10-2-Debian <<>> timeout.yourdomain.com @127.0.0.1
;; global options: +cmd
;; no servers could be reached

Download PCAP File

In TCP mode, the behavior is identical. The client is unable to receive any response. Once again, the client makes three attempts to resolve the timeout:

# dig timeout.yourdomain.com @127.0.0.1 +tcp

;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out

; <<>> DiG 9.18.10-2-Debian <<>> timeout.yourdomain.com @127.0.0.1 +tcp
;; global options: +cmd
;; no servers could be reached

Download PCAP File

Like other features, you can append anything to the feature name to avoid receiving cached responses from the target DNS resolver. This forces the target resolver to actively communicate with our PolarDNS server instead of responding with cached answers. Using a random number is the most effective strategy:

# dig timeout${RANDOM}.yourdomain.com @10.211.55.2

;; communications error to 10.211.55.2#53: timed out
;; communications error to 10.211.55.2#53: timed out
;; communications error to 10.211.55.2#53: timed out

; <<>> DiG 9.18.10-2-Debian <<>> timeout32124.yourdomain.com @10.211.55.2
;; global options: +cmd
;; no servers could be reached

Download PCAP File

From the same category

Go back to catalogue.