NsChain - NS Alias Chains

NsChain - NS Alias Chains

This module implements incremental alias chains using NS (Name Server) records. It returns an alias record with an incremented domain name index, forming a chain that continues to increment indefinitely.

Specifically, this module generates a NS alias record in the format nschain###.yourdomain.com, where ### represents the incremented index.

The concept is that if the client/resolver attempts to resolve this alias further, it will generate yet another incremented alias, causing the process to continue indefinitely and potentially keeping the resolver occupied.

However, in practice, most modern resolvers detect such chains and terminate the resolution after encountering a certain number of consecutive aliases (e.g., 20 aliases) or upon reaching a specified time limit for the resolution (e.g., 30 seconds).

Note that this feature provides the same functionality as requesting a NS record for the generic chain feature.

⚠BEWARE⚠This could potentially lead to a domain lock-up (DoS).

Category: Alias chains

Tags: Domain Lock-Up, Denial of Service

RFCs: RFC1035

Format 

nschain<NUMBER>.yourdomain.com

Where:

  • The <NUMBER> parameter specifies an arbitrary number that will be incremented in the response.

Examples

By default, the module generates an NS alias record with the index of 1:

# dig nschain.yourdomain.com @127.0.0.1

; <<>> DiG 9.18.10-2-Debian <<>> nschain.yourdomain.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 651
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nschain.yourdomain.com.		IN	A

;; ANSWER SECTION:
nschain.yourdomain.com.	60	IN	NS	nschain1.yourdomain.com.

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Nov 08 23:24:13 +04 2024
;; MSG SIZE  rcvd: 77

Download PCAP File


If we attempt to resolve the resulting domain name (nschain1.yourdomain.com), we receive an incremented alias record:

# dig nschain1.yourdomain.com @127.0.0.1

; <<>> DiG 9.18.10-2-Debian <<>> nschain1.yourdomain.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3227
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nschain1.yourdomain.com.	IN	A

;; ANSWER SECTION:
nschain1.yourdomain.com. 60	IN	NS	nschain2.yourdomain.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Nov 08 23:24:15 +04 2024
;; MSG SIZE  rcvd: 78

Download PCAP File


If we continue to resolve the next domain name (nschain2.yourdomain.com), we again receive an incremented alias record:

# dig nschain2.yourdomain.com @127.0.0.1

; <<>> DiG 9.18.10-2-Debian <<>> nschain2.yourdomain.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41467
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nschain2.yourdomain.com.	IN	A

;; ANSWER SECTION:
nschain2.yourdomain.com. 60	IN	NS	nschain3.yourdomain.com.

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Nov 08 23:24:16 +04 2024
;; MSG SIZE  rcvd: 78

Download PCAP File


This resolution process can continue indefinitely, as there are no limits on the size of the index number. Each resolution yields another incremented alias record:

# dig nschain9999999999999999999999999.yourdomain.com @127.0.0.1

; <<>> DiG 9.18.10-2-Debian <<>> nschain9999999999999999999999999.yourdomain.com @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62405
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nschain9999999999999999999999999.yourdomain.com. IN A

;; ANSWER SECTION:
nschain9999999999999999999999999.yourdomain.com. 60 IN NS nschain10000000000000000000000000.yourdomain.com.

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Fri Nov 08 23:24:17 +04 2024
;; MSG SIZE  rcvd: 127

Download PCAP File

The domain name will never be fully resolved as the incremental process continues indefinitely.


From the same category

See also


Go back to catalogue.