NsAlias - Random NS Aliases

NsAlias - Random NS Aliases

This module is designed to return one or more random aliases using NS (Name Server) records.

It specifically generates a random NS alias record in the format nsalias######.yourdomain.com, where ###### represents a random number.

The idea is that if the client/resolver decides to resolve this further, it will result in the generation of yet another alias, theoretically leading to a resolution of infinite chain of random aliases. In practice, however, most modern resolvers will terminate the resolution after encountering several consecutive alias records.

Note that this feature provides the same functionality as requesting the NS record for the generic alias feature. Responding with multiple records (aliases) in a single response is also supported.

⚠BEWARE⚠This can potentially lead to amplification effect (DoS) or domain lock-up (DoS).

Category: Aliases

Tags: Amplification, Domain Lock-Up, Denial of Service

RFCs: RFC1035

Format 

nsalias.<NUMBER>.yourdomain.com

Where:

  • The <NUMBER> parameter defines how many aliases should be generated in the response.

Examples

By default, it returns a single NS alias:

# dig nsalias.yourdomain.com @127.0.0.1

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

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

;; ANSWER SECTION:
nsalias.yourdomain.com.	60	IN	NS	nsalias819058.yourdomain.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Wed Oct 16 09:37:12 +04 2024
;; MSG SIZE  rcvd: 82

Download PCAP File


Same example as above, but this time we explicitly specify that we want to receive a single NS record:

# dig nsalias.1.yourdomain.com @127.0.0.1

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

;; QUESTION SECTION:
;nsalias.1.yourdomain.com.	IN	A

;; ANSWER SECTION:
nsalias.1.yourdomain.com. 60	IN	NS	nsalias328570.1.yourdomain.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Wed Oct 16 09:37:14 +04 2024
;; MSG SIZE  rcvd: 86

Download PCAP File


In this case, we specify that we want to receive five NS aliases:

# dig nsalias.5.yourdomain.com @127.0.0.1

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

;; QUESTION SECTION:
;nsalias.5.yourdomain.com.	IN	A

;; ANSWER SECTION:
nsalias.5.yourdomain.com. 60	IN	NS	nsalias486130.5.yourdomain.com.
nsalias.5.yourdomain.com. 60	IN	NS	nsalias559338.5.yourdomain.com.
nsalias.5.yourdomain.com. 60	IN	NS	nsalias36708.5.yourdomain.com.
nsalias.5.yourdomain.com. 60	IN	NS	nsalias928003.5.yourdomain.com.
nsalias.5.yourdomain.com. 60	IN	NS	nsalias591080.5.yourdomain.com.

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Wed Oct 16 09:37:15 +04 2024
;; MSG SIZE  rcvd: 261

Download PCAP File


From the same category

See also


Go back to catalogue.