> For the complete documentation index, see [llms.txt](https://ceh-practical.cavementech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ceh-practical.cavementech.com/module-4.-enumeration/5.-dns-enumeration.md). # 5. DNS Enumeration ## 1. DNS Enumeration using zone transfer ### dig find the nameserver of a domain ``` dig ns zonetransfer.me ```

Now try the zone transfer for the domain from its primary and secondary name servers ``` dig axfr zonetransfer.me @nsztm2.digi.ninja ```

### nslookup Fire up the tool on windows ``` nslookup set querytype=soa ```

Now execute the zone transfer ``` ls -d nsztm2.digi.ninja ``` ## 2. Zone transfer using DNSSEC transfer {% embed url="" %} ``` ./dnsrecon.py -d zonetransfer.me -z ``` {% hint style="info" %} -d target domain -z DNSSEC Zone walk {% endhint %}

**Other tools** {% embed url="" %} ## 3. DNS Enumeration using Nmap ``` nmap --script=broadcast-dns-service-discovery zonetransfer.me ```

DNS brute forcing ``` nmap -T5 -p 53 --script dns-brute zonetransfer.me ```

common service records ``` nmap --script dns-srv-enum --script-args "dns-srv-enum.domain='zonetransfer.me'" ``` {% embed url="" %} {% embed url="" %} {% embed url="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ceh-practical.cavementech.com/module-4.-enumeration/5.-dns-enumeration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.