> For the complete documentation index, see [llms.txt](https://xedex.gitbook.io/internalpentest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xedex.gitbook.io/internalpentest/internal-pentest/active-directory/domain-name-and-domain-controllers.md).

# Reconnaissance

 This section can be used before and after the initial attack vectors

### Using simple CMD

#### Domain name

```
ipconfig /all
```

#### Domain Controllers

```
nslookup <domain>
```

```
nltest /dclist:{domainname}
```

```
echo %logonserver%
```

## On Linux

#### Domain name

```
cat /etc/resolv.conf
```

Or scan machines with CrackMapExec:

```
cme smb 192.168.12.0/24
```

#### Domain controller

As domain controllers are often DNS Servers, you can simply use these commands:

```bash
systemd-resolve --status | grep "DNS Servers"
```

or :

```bash
nmcli dev show | grep DNS
```

For more, i suggest to visit @aas notebook here :

{% embed url="<https://lydericlefebvre.gitbook.io/cheatsheet/internalpentest/active-directory/reconnaissance>" %}


---

# 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://xedex.gitbook.io/internalpentest/internal-pentest/active-directory/domain-name-and-domain-controllers.md?ask=<question>&goal=<endgoal>
```

`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.