> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/getting-started/04-dns.md).

# Step 3 — DNS

With your VM deployed, point your chosen domain to the VM's public IP address. DNS changes typically propagate within a few minutes, though it can take longer depending on your provider.

{% stepper %}
{% step %}
**Get the VM's public IP address**

In the Azure Portal, navigate to the **Public IP resource** that was created with your deployment and copy the IP address.
{% endstep %}

{% step %}
**Add a DNS A record**

With your DNS provider, add the following record:

| Type | Name                              | Value                       |
| ---- | --------------------------------- | --------------------------- |
| `A`  | `sync` (or your chosen subdomain) | Your VM's public IP address |

For example, if your domain is `yourcompany.com` and your subdomain is `sync`, the record should point `sync.yourcompany.com` to the VM's IP.
{% endstep %}

{% step %}
**Confirm the record resolves**

Before continuing, verify that your domain now points to the VM's IP. From any terminal, run:

```
nslookup <your-domain>
```

The output should show your VM's public IP address. You can also use an online DNS lookup tool if you do not have a terminal available. Once the record resolves correctly, you are ready to continue.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Once DNS resolves, AOH Sync obtains a TLS certificate for your domain automatically. If you prefer to supply your own certificate, you can upload a `.crt`/`.pem` file and private key (or paste PEM) in the browser setup wizard in [Step 4 — First Login](/getting-started/05-first-login.md).
{% endhint %}

## How to check it worked

Running `nslookup <your-domain>` (or an equivalent DNS lookup) returns your VM's public IP address.

## Related

* [Step 2 — Azure Marketplace](/getting-started/03-deploy.md)
* [Step 4 — First Login](/getting-started/05-first-login.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aohwv.dev/getting-started/04-dns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.