> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/ip-addressing-and-routing/about-restricted-dns-entries.md).

# About restricted DNS entries

## About restricted DNS entries <a href="#aboutrestricteddnsentries" id="aboutrestricteddnsentries"></a>

Some customers require restricted internet access for their devices, to ensure that the devices cannot access the internet beyond a limited set of trusted IP addresses.

Eseye can restrict internet access using two separate filters:

* **Allowed List** – a customer-defined list of permitted domains or IP addresses. Only queries for the permitted domains and IP addresses are resolved. All other traffic is dropped.
* **Blocked List** – an Eseye-defined list of harmful domains or IP addresses. If a domain is on the Blocked List, Eseye will not resolve the corresponding IP addresses for that domain. If an IP address is on the Blocked List, Eseye will drop all traffic from that address.

Having both lists ensures that compromised devices cannot access malicious web content that might be used to gain control of the device.

{% hint style="info" %}
The lists can use domain names or fully qualified domain names (FQDNs).
{% endhint %}

The examples below show scenarios in which this customised DNS service is required.

#### Example 1 – router sending debug data to router manufacturer

If the router manufacturer URL or FQDN is not on the Allowed List, the request is dropped. We recommend you prevent your router from performing these lookups within its normal operation.

#### Example 2 – domains permitted but forwarded to other servers for resolution

Certain domains are permitted. However, the request is forwarded to designated DNS servers to ultimately resolve and return the response.

{% hint style="info" %}
Contact your Account Manager if you have specific DNS requirements.
{% endhint %}


---

# 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.eseye.com/anynet-sim/connectivity/ip-addressing-and-routing/about-restricted-dns-entries.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.