github.com/StackExchange/dnscontrol/v4@v4.11.0/documentation/provider/bunny_dns.md (about) 1 # Configuration 2 3 To use this provider, add an entry to `creds.json` with `TYPE` set to `BUNNY_DNS` along with 4 your [Bunny API Key](https://dash.bunny.net/account/settings). 5 6 Example: 7 8 {% code title="creds.json" %} 9 ```json 10 { 11 "bunny_dns": { 12 "TYPE": "BUNNY_DNS", 13 "api_key": "your-bunny-api-key" 14 } 15 } 16 ``` 17 {% endcode %} 18 19 You can also use environment variables: 20 21 ```shell 22 export BUNNY_DNS_API_KEY=XXXXXXXXX 23 ``` 24 25 {% code title="creds.json" %} 26 ```json 27 { 28 "bunny_dns": { 29 "TYPE": "BUNNY_DNS", 30 "api_key": "$BUNNY_DNS_API_KEY" 31 } 32 } 33 ``` 34 {% endcode %} 35 36 ## Metadata 37 38 This provider does not recognize any special metadata fields unique to Bunny DNS. 39 40 ## Usage 41 42 An example configuration: 43 44 {% code title="dnsconfig.js" %} 45 ```javascript 46 var REG_NONE = NewRegistrar("none"); 47 var DSP_BUNNY_DNS = NewDnsProvider("bunny_dns"); 48 49 D("example.com", REG_NONE, DnsProvider(DSP_BUNNY_DNS), 50 A("test", "1.2.3.4"), 51 END); 52 ``` 53 {% endcode %} 54 55 # Activation 56 57 DNSControl depends on the [Bunny API](https://docs.bunny.net/reference/bunnynet-api-overview) to manage your DNS 58 records. You will need to generate an [API key](https://dash.bunny.net/account/settings) to use this provider. 59 60 ## New domains 61 62 If a domain does not exist in your Bunny account, DNSControl will automatically add it with the `push` command. 63 64 ## Caveats 65 66 - Bunny DNS does not support dual-hosting or configuring custom TTLs for NS records on the zone apex. 67 - While custom nameservers are properly recognized by this provider, it is currently not possible to configure them. 68 - Any custom record types like Script, Redirect, Flatten or Pull Zone are currently not supported by this provider. Such 69 records will be completely ignored by DNSControl and left as-is.