Bunny DNS

Configuration

To use this provider, add an entry to creds.json with TYPE set to BUNNY_DNS along with your Bunny API Key.

Example:

creds.json

{
  "bunny_dns": {
    "TYPE": "BUNNY_DNS",
    "api_key": "your-bunny-api-key"
  }
}

You can also use environment variables:

export BUNNY_DNS_API_KEY=XXXXXXXXX

creds.json

{
  "bunny_dns": {
    "TYPE": "BUNNY_DNS",
    "api_key": "$BUNNY_DNS_API_KEY"
  }
}

Metadata

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

Usage

An example configuration:

dnsconfig.js

var REG_NONE = NewRegistrar("none");
var DSP_BUNNY_DNS = NewDnsProvider("bunny_dns");

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

Activation

DNSControl depends on the Bunny API to manage your DNS records. You will need to generate an API key to use this provider.

New domains

If a domain does not exist in your Bunny account, DNSControl will automatically add it with the push command.

Custom record types

DNSControl supports only the custom record types listed below for Bunny DNS. Other Bunny-specific types (such as Script or Flatten) are not supported and will be ignored by DNSControl and left as-is.

Redirect

You can configure Bunny's Redirect type with BUNNY_DNS_RDR:

dnsconfig.js

    BUNNY_DNS_RDR("@", "https://foo.bar"),

Pull Zone (PZ)

You can configure Bunny's Pull Zone type with BUNNY_DNS_PZ. The target is the Pull Zone ID:

dnsconfig.js

    BUNNY_DNS_PZ("@", 12345),

Caveats

• Bunny DNS does not support dual-hosting or configuring custom TTLs for NS records on the zone apex.

• While custom nameservers are properly recognized by this provider, it is currently not possible to configure them.