> For the complete documentation index, see [llms.txt](https://docs.dnscontrol.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dnscontrol.org/provider/dynadot.md).

# Dynadot

DNSControl's Dynadot provider supports being a Registrar. Support for being a DNS Provider is not included, but could be added in the future.

### Configuration

To use this provider, add an entry to `creds.json` with `TYPE` set to `DYNADOT` along with `key` from the [Dynadot API](https://www.dynadot.com/account/domain/setting/api.html).

Example:

{% code title="creds.json" %}

```json
{
  "dynadot": {
    "TYPE": "DYNADOT",
    "key": "API Key",
  }
}
```

{% endcode %}

### Metadata

This provider does not recognize any special metadata fields unique to Dynadot.

### Usage

An example configuration:

{% code title="dnsconfig.js" %}

```javascript
var REG_DYNADOT = NewRegistrar("dynadot");

DOMAIN_ELSEWHERE("example.com", REG_DYNADOT, [
    "ns1.example.net.",
    "ns2.example.net.",
    "ns3.example.net.",
]);
```

{% endcode %}

### Activation

You must [enable the Dynadot API](https://www.dynadot.com/account/domain/setting/api.html) for your account and whitelist the IP address of the machine that will run DNSControl.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.dnscontrol.org/provider/dynadot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.