# Gidinet

### Configuration

To use this provider, add an entry to `creds.json` with `TYPE` set to `GIDINET` along with your Gidinet account credentials.

Example:

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

```json
{
  "gidinet": {
    "TYPE": "GIDINET",
    "username": "your-gidinet-username",
    "password": "your-gidinet-password"
  }
}
```

{% endcode %}

The [creds.json](/commands/creds-json.md#example-commands) page in the docs explains how you can generate this dynamically so you can pull the secret token from 1Password or the vault of your choosing.

### Metadata

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

### Usage

#### As DNS Provider only

If you manage your domain registration elsewhere but want to use Gidinet for DNS:

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

```javascript
var REG_NONE = NewRegistrar("none");
var DSP_GIDINET = NewDnsProvider("gidinet");

D("example.com", REG_NONE, DnsProvider(DSP_GIDINET),
    A("test", "1.2.3.4"),
);
```

{% endcode %}

#### As both Registrar and DNS Provider

If your domain is registered with Gidinet and you want to manage both nameserver delegation and DNS records:

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

```javascript
var REG_GIDINET = NewRegistrar("gidinet");
var DSP_GIDINET = NewDnsProvider("gidinet");

D("example.com", REG_GIDINET, DnsProvider(DSP_GIDINET),
    A("test", "1.2.3.4"),
);
```

{% endcode %}

#### As Registrar only (DNS hosted elsewhere)

If your domain is registered with Gidinet but you want to use a different DNS provider:

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

```javascript
var REG_GIDINET = NewRegistrar("gidinet");
var DSP_OTHER = NewDnsProvider("cloudflare");

D("example.com", REG_GIDINET, DnsProvider(DSP_OTHER),
    A("test", "1.2.3.4"),
);
```

{% endcode %}

When used as a registrar, Gidinet will manage the nameserver delegation at the registry level.

### Activation

1. Log in to the [Gidinet Control Panel](https://www.gidinet.com/)
2. Your account credentials (username and password) are the same ones you use to log in to the control panel

### Supported record types

The Gidinet DNS API supports the following record types:

| Name  | Description                                                        |
| ----- | ------------------------------------------------------------------ |
| A     | IPv4 address record                                                |
| AAAA  | IPv6 address record                                                |
| CNAME | Canonical name (alias) record                                      |
| MX    | Mail exchange record                                               |
| NS    | Name server record (subdomains only, apex NS managed by registrar) |
| TXT   | Text record                                                        |
| SRV   | Service record                                                     |

### Unsupported record types

The following record types are **not supported** by Gidinet:

* `ALIAS` - Not available
* `CAA` - Only available with premium service
* `DHCID`, `DNAME`, `DNSKEY`, `DS`, `HTTPS`, `LOC`, `NAPTR`, `PTR`, `SOA`, `SSHFP`, `SVCB`, `TLSA` - Not available

### Limitations

#### TTL values

Gidinet only supports specific TTL values. If you specify a TTL that is not in the allowed list, DNSControl will automatically round up to the nearest allowed value.

Allowed TTL values (in seconds):

* 60 (1 minute)
* 300 (5 minutes)
* 600 (10 minutes)
* 900 (15 minutes)
* 1800 (30 minutes)
* 2700 (45 minutes)
* 3600 (1 hour)
* 7200 (2 hours)
* 14400 (4 hours)
* 28800 (8 hours)
* 43200 (12 hours)
* 64800 (18 hours)
* 86400 (1 day)
* 172800 (2 days)

#### Nameservers

Gidinet's default nameservers are:

* `dnsl1.gidinet.com`
* `dnsl2.gidinet.com`

**Apex NS records are automatically filtered** by the DNS provider with a warning message. Gidinet does not support modifying NS records at the zone apex via the DNS API - they are managed by the registrar.

To manage nameserver delegation, use Gidinet as a **registrar** with the `NAMESERVER()` function:

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

```javascript
var REG_GIDINET = NewRegistrar("gidinet");
var DSP_GIDINET = NewDnsProvider("gidinet");

D("example.com", REG_GIDINET, DnsProvider(DSP_GIDINET),
    NAMESERVER("dnsl1.gidinet.com."),
    NAMESERVER("dnsl2.gidinet.com."),
    A("test", "1.2.3.4"),
);
```

{% endcode %}

This uses the Core API's `domainNameServersChange` method to update the nameservers at the registry level.

#### Zone creation

Zones must be created via the Gidinet web interface. The API does not support creating new zones.

#### Zone listing

The provider supports listing all zones in your account via `dnscontrol get-zones`. This uses the Core API's `domainGetList` method to retrieve all active domains.

#### Concurrent operations

The provider does not support concurrent API operations. Changes are applied sequentially to ensure reliability.


---

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