Self-host CoreDNS with Levelrail

Plugin based DNS server on the official image. The install form carries the Corefile as an editable file, so it starts as a caching forwarder with health and readiness endpoints.

  • Authorcoredns
  • LicenceApache-2.0
  • Memory64 MiB
  • Services1

How to self-host CoreDNS

  1. Pull the images

    One image is pulled on your server.

    Show images
    • coredns/coredns:1.15.0
  2. Create the app

    One service starts in a single Compose app, on ports 8080, 1053.

  3. Fill in the secrets

    You do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Point a client at the DNS port to resolve through the cache, then edit the Corefile setting to add zones, rewrites or other plugins.

CoreDNS requirements

Memory
About 64 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8080, 1053
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then CoreDNS. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the CoreDNS docs page.

Deploy CoreDNS your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy CoreDNS from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain coredns=app.example.com.

levelrail-cli templates install coredns --name my-coredns

Deploy CoreDNS with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/coredns/install \
  -d '{
    "name": "my-coredns"
  }'

CoreDNS configuration

CoreDNS services

ServiceImagePortsVolumes
coredns coredns/coredns:1.15.0 8080, 1053 none

CoreDNS environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
8080, 1053
Volumes
none

CoreDNS FAQ

How much memory does CoreDNS need?

The catalog lists about 64 MiB of memory for CoreDNS.

Does CoreDNS run on arm64?

For CoreDNS, arm64 support is not confirmed; amd64 is unknown.

What licence is CoreDNS under?

CoreDNS is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does CoreDNS need configuration before it starts?

No. The template fills in its own defaults.

Which ports does CoreDNS use?

CoreDNS listens on ports 8080 and 1053 inside the stack.

Can I deploy CoreDNS on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for CoreDNS, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image coredns/coredns:1.15.0 is what you deploy there.

levelrail-cli templates install coredns --name my-coredns