The Cloudflare module allows automatic creation of DNS Records in Cloudflare.
These can be made for any type of services - from BungeeCord to vanilla servers. It can handle multiple domains.
To enable it, you need a domain with NameServers by Cloudflare. The module needs your
E-Mail, the Global API Key and the zoneId OR
a Cloudflare API Token. Everything can be found or created in the Cloudflare dashboard.
If the cluster is being used, the configuration must be set up for each node individually, this avoids unintentional entries such as nodes that are within an internal LAN and can only be reached via specific ports or proxy servers.
The configuration contains a JsonArray of entry objects. You will need one entry per domain you want to support.
Enables or disables the entry (
The authenticationMethod you want to use (
We recommend to use
BEARER_TOKEN because it provides more security.
You can restrict the access to certain domains on your accounts and to certain IP-Adresses.
The Global API Key provides access to all your domains and the domains of accounts where you are a registered member.
The hostAddress the Cloudflare Entries should have. (e.g.
This has to be your external IP-Address (NOT
The E-Mail address of your Cloudflare account. Can be left empty when using
BEARER_TOKEN as authentication method!
Your Global API Key or created Bearer Token
The zoneId of your DNS zone
Your domain name (e.g.
JsonArray of groups for which DNS records should be created
The name of the group
The subdomain on which the group should be reached. (e.g.
@ means the group is accessible through the domain set in domainName without any subdomain (e.g.
The priority for the created SRV-Record
The weight for the created SRV-Record
The default configuration for the CloudFlare Module looks like this: