> 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/realtimeregister.md).

# Realtime Register

[realtimeregister.com](https://realtimeregister.com) is a domain registrar based in the Netherlands.

### Configuration

To use this provider, add an entry to `creds.json` with `TYPE` set to `REALTIMEREGISTER` along with your API-key. Further configuration includes a flag indicating BASIC or PREMIUM DNS-service and a flag indicating the use of the sandbox environment

**Example:**

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

```json
{
  "realtimeregister": {
    "TYPE": "REALTIMEREGISTER",
    "apikey": "abcdefghijklmnopqrstuvwxyz1234567890",
    "sandbox" : "0",
    "premium" : "0"
  }
}
```

{% endcode %}

If sandbox is omitted or set to any other value than "1" the production API will be used. If premium is set to "1", you will only be able to update zones using Premium DNS. If it is omitted or set to any other value, you will only be able to update zones using Basic DNS.

**Important Notes**:

* It is recommended to create a 'DNSControl' user in your account settings with limited permissions (i.e. VIEW\_DNS\_ZONE, CREATE\_DNS\_ZONE, UPDATE\_DNS\_ZONE, VIEW\_DOMAIN, UPDATE\_DOMAIN), otherwise anyone with access to this `creds.json` file might have *full* access to your RTR account and will be able to transfer or delete your domains.

### Metadata

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

### Usage

An example `dnsconfig.js` configuration file

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

```javascript
var REG_RTR = NewRegistrar("realtimeregister");
var DSP_RTR = NewDnsProvider("realtimeregister");

D("example.com", REG_RTR, DnsProvider(DSP_RTR),
    A("test", "1.2.3.4"),
);
```

{% endcode %}


---

# 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/realtimeregister.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.