# Netlify

### Configuration

To use this provider, add an entry to `creds.json` with `TYPE` set to `NETLIFY` along with a Netlify account personal access token. You can also optionally add an account slug. This is *typically* your username on Netlify.

Examples:

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

```json
{
  "netlify": {
    "TYPE": "NETLIFY",
    "token": "your-netlify-account-access-token",
    "slug": "account-slug" // this is optional
  }
}
```

{% endcode %}

### Metadata

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

### Usage

An example configuration:

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

```javascript
var REG_NETLIFY = NewRegistrar("netlify");
var DSP_NETLIFY = NewDnsProvider("netlify");

D("example.com", REG_NETLIFY, DnsProvider(DSP_NETLIFY),
    A("test", "1.2.3.4"),
);
```

{% endcode %}

### Activation

DNSControl depends on a Netlify account personal access token.

### Caveats

Empty MX records are not supported.


---

# Agent Instructions: 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.dnscontrol.org/provider/netlify.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.