github.com/StackExchange/dnscontrol/v4@v4.11.0/documentation/provider/desec.md (about)

     1  ## Configuration
     2  
     3  To use this provider, add an entry to `creds.json` with `TYPE` set to `DESEC`
     4  along with a deSEC account auth token.
     5  
     6  Example:
     7  
     8  {% code title="creds.json" %}
     9  ```json
    10  {
    11    "desec": {
    12      "TYPE": "DESEC",
    13      "auth-token": "your-deSEC-auth-token"
    14    }
    15  }
    16  ```
    17  {% endcode %}
    18  
    19  ## Metadata
    20  This provider does not recognize any special metadata fields unique to deSEC.
    21  
    22  ## Usage
    23  An example configuration:
    24  
    25  {% code title="dnsconfig.js" %}
    26  ```javascript
    27  var REG_NONE = NewRegistrar("none");
    28  var DSP_DESEC = NewDnsProvider("desec");
    29  
    30  D("example.com", REG_NONE, DnsProvider(DSP_DESEC),
    31      A("test", "1.2.3.4"),
    32  END);
    33  ```
    34  {% endcode %}
    35  
    36  ## Activation
    37  DNSControl depends on a deSEC account auth token.
    38  This token can be obtained by [logging in via the deSEC API](https://desec.readthedocs.io/en/latest/auth/account.html#log-in).
    39  
    40  {% hint style="warning" %}
    41  deSEC enforces a daily limit of 300 RRset creation/deletion/modification per
    42  domain. Large changes may have to be done over the course of a few days.  The
    43  integration test suite can not be run in a single session. See
    44  [https://desec.readthedocs.io/en/latest/rate-limits.html#api-request-throttling](https://desec.readthedocs.io/en/latest/rate-limits.html#api-request-throttling)
    45  {% endhint %} 
    46