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

# NS1

Firefly integrates with NS1 to pull in information about your DNS records and zones as "assets". This means in your Firefly Inventory, you'll see NS1 DNS records listed (with their configurations) just like cloud assets. You can then enforce IaC or policies on them as well (for example, ensuring all DNS records follow a naming convention).

## Prerequisites

* An NS1 account with administrative access.
* An NS1 API key with appropriate permissions.
* Access to NS1 API endpoints.
* Ability to manage API keys.

## Setup Procedure

1. Log in to your NS1 account.
2. Create an API Key by following the instructions in the [NS1 API Key Management Guide](https://help.ns1.com/hc/en-us/articles/360017341694-Managing-API-keys#idm45892557001984).
3. In Firefly, click **Settings > Integrations**.
4. Click **Add New > NS1**.
5. Enter a descriptive name in the Nickname field.
6. Copy and paste your API key into the API Key field.
7. Click **Next**.
8. Click **Done**.

## Configuration Details

* Firefly scans every 8 hours by default for SaaS data.
* Your NS1 DNS records list will stay updated automatically.
* You can enforce IaC or policies on your NS1 assets.
* Supports monitoring of NS1 DNS records and zones.


---

# 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.firefly.ai/integrations/data-sources/ns1.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.