# MythicBeasts


<!-- Code generated by gen-dns-providers; DO NOT EDIT. -->

Configuration for the [MythicBeasts](https://www.mythic-beasts.com/) DNS provider.

See the [lego documentation](https://go-acme.github.io/lego/dns/mythicbeasts/) for full details.

```yaml
letsEncrypt:
  dnsProvider: "mythicbeasts"
  dnsCredentials:
    # MYTHICBEASTS_PASSWORD: Password
    password: ""
    # MYTHICBEASTS_USERNAME: User name
    username: ""
    # MYTHICBEASTS_API_ENDPOINT: The endpoint for the API (must implement v2)
    apiEndpoint: ""
    # MYTHICBEASTS_AUTH_API_ENDPOINT: The endpoint for Mythic Beasts' Authentication
    authAPIEndpoint: ""
    # MYTHICBEASTS_POLLING_INTERVAL: Time between DNS propagation check in seconds (Default: 2)
    pollingInterval: ""
    # MYTHICBEASTS_PROPAGATION_TIMEOUT: Maximum waiting time for DNS propagation in seconds (Default: 60)
    propagationTimeout: ""
    # MYTHICBEASTS_TTL: The TTL of the TXT record used for the DNS challenge in seconds (Default: 120)
    ttl: ""
```

Credentials are passed directly to lego using strong types and are never written to the process environment.
You may also use the raw lego environment-variable names as keys instead of the normalized names.