> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/netodns/configure-netodns.md).

# Configure NetoDNS

*You can run NetoDNS with the default configuration, which should be sufficient for most deployments.*

## Modifying the configuration

NetoDNS uses environment variables to set configuration. All configuration uses the prefix `NETO_`

Follow the steps in the install instructions for your chosen deployment method to edit and pass the configuration settings:

[Install NetoDNS (container)](https://docs.fusion.vectra.ai/netodns/install-netodns-container.md) or [Install NetoDNS (Linux package)](https://docs.fusion.vectra.ai/netodns/install-netodns-linux-package.md)

## Configuration settings

| **Environment Variable**  | **Description**                                                        | **Default Value** | **Example**                                                    |
| ------------------------- | ---------------------------------------------------------------------- | ----------------- | -------------------------------------------------------------- |
| `NETO_PROTOCOL`           | Protocol to listen on (e.g., `tcp`, `udp`).                            | `tcp`             | `NETO_PROTOCOL=udp`                                            |
| `NETO_PORT`               | Port to listen on.                                                     | `514`             | `NETO_PORT=10514`                                              |
| `NETO_OUTPUT_FILE`        | Path to the output file where logs are written.                        | None              | `NETO_OUTPUT_FILE=/var/log/netodns.log`                        |
| `NETO_DATASRC`            | Data source identifier for processing logs.                            | None              | `NETO_DATASRC=EXAMPLE-SOURCE`                                  |
| `NETO_EXCLUDE_QUERIES`    | Comma-separated list of query names to exclude.                        | None              | `NETO_EXCLUDE_QUERIES=example.com,foo.com`                     |
| `NETO_EXCLUDE_QUERIES_RE` | Comma-separated list of regular expressions for excluding query names. | None              | `NETO_EXCLUDE_QUERIES_RE=.*\\.example\\.com$,.*\\.test\\.com$` |
| `NETO_INTERVAL`           | Interval for periodic tasks (in seconds).                              | `30`              | `NETO_INTERVAL=60`                                             |
| `NETO_ENDPOINT__APPNAME`  | Application name for the endpoint.                                     | None              | `NETO_ENDPOINT__APPNAME=my-app`                                |
| `NETO_ENDPOINT__CUSTOMER` | Customer identifier for the endpoint.                                  | None              | `NETO_ENDPOINT__CUSTOMER=my-customer`                          |
| `NETO_NETOSECRET`         | API key used for authenticating to Fusion                              | None              | `NETO_NETOSECRET=my-secret-key`                                |
| `NETO_PROXY__ENABLED`     | Whether to enable proxy support (true/false).                          | `false`           | `NETO_PROXY__ENABLED=true`                                     |
| `NETO_PROXY__URL`         | URL of the proxy server.                                               | None              | `NETO_PROXY__URL=http://proxy.example.com`                     |
| `NETO_ENDPOINT__RETRYMIN` | Minimum retry interval for token requests (in seconds).                | `300`             | `NETO_ENDPOINT__RETRYMIN=5`                                    |
| `NETO_ENDPOINT__RETRYMAX` | Maximum retry interval for token requests (in seconds).                | `600000`          | `NETO_ENDPOINT__RETRYMAX=300000`                               |


---

# 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.fusion.vectra.ai/netodns/configure-netodns.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.
