# DNS

It is possible to enumerate the domain using the DNS protocol. This will give you the fully identifiable domain name (FQDN) and other information about the roles of the target machine.

{% tabs %}
{% tab title="Dig" %}

```bash
Dig -t SRV _gc._tcp.<FQDN>

Dig -t SRV _ldap._tcp.<FQDN>

Dig -t SRV _kerberos._tcp.<FQDN>

Dig -t SRV _kpasswd._tcp.<FQDN>
```

{% endtab %}

{% tab title="Nmap" %}

```python
nmap --script dns-srv-enum -script-args "dns-srv-enum.domain='<FQDN>'"
```

{% endtab %}
{% endtabs %}

In Active Directory-integrated DNS, reverse lookups are used to resolve IP addresses to host names. This operation relies on DNS PTR records. It allows finding the names of the hosts of a network.

```
nslookup <DOMAIN.COM>

nslookup -type=srv _kerberos._tcp.DOMAIN.COM
nslookup -type=srv _kpasswd._tcp.DOMAIN.COM
nslookup -type=srv _ldap._tcp.DOMAIN.COM
nslookup -type=srv _ldap._tcp.dc._msdcs.DOMAIN.COM
```


---

# Agent Instructions: 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:

```
GET https://blog.hacktive.bebzounette.com/active-directory/untitled/dns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
