> For the complete documentation index, see [llms.txt](https://docs.noto.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noto.network/noto-api-docs/test-web3-domain-resolution-over-dns.md).

# Test Web3 domain resolution over DNS

NOTO offers a set of DNS resolvers that can be used for testing purposes.

| Type               | Address                     |
| ------------------ | --------------------------- |
| DNS - over - HTTPS | <https://dns1.noto.network> |
| NS1                | 34.154.40.173               |
| NS2                | 34.154.254.177              |

Please bear in mind that:

* Being able to fully interact with a Web3 domain depends only in part on its resolution, whether this happens directly from the blockchain or via a DNS query on our nameservers. This depends on factors such as the browser or application you are using and it is beyond the control of Freename.
* These DNS servers are intended to facilitate testing but are not meant to permanently replace the DNS server provided by your ISP. Should you have any issues while using the Freename DNS, please switch back to your original DNS configuration.

<br>


---

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

```
GET https://docs.noto.network/noto-api-docs/test-web3-domain-resolution-over-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.