Lancache-DNS

This docker container provides DNS entries for caching services to be used in conjunction with a container.

  • Network Services
  • Tools & Utilities
This docker container provides DNS entries for caching services to be used in conjunction with a container. The DNS is generated automatically at startup of the container

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
70last commit 54 days ago
Popular
50322 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 55 days ago

GitHub stars
322
Open issues
14
Last commit
2026-09-27
License
MIT
Activity
stale

Checked 22 days ago - source: GitHub (lancachenet/lancache-dns)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Clone, edit .env, start the cache On a Linux machine with Docker already installed, clone the Lancache docker-compose folder, open the .env file (your main settings file) to fill in your choices, then run docker compose up -d to start the containers. If you skip the .env step or start with incomplete settings, the cache may use defaults or not fit your network. source
  • Make your router use only Lancache-DNS After the containers start, set your router so it sends DNS (the system that turns website names into addresses) requests only to the Lancache-DNS container. Without this, devices may go directly to normal DNS servers and your traffic will not pass through the cache. source
  • Missing CONFIGHASH can be normal If startup says it could not find CONFIGHASH for existing cachedata, that is a saved fingerprint of your cache settings, and the container can create one from the current live configuration. You usually do not need to worry unless you deleted it on purpose or are upgrading from an older setup. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Community

Collected 54 days ago - public community threads