PlugNPiN

PlugNPiN scans labelled Docker containers and automatically creates local DNS records in Pi-hole or AdGuard Home plus matching Nginx Proxy Manager proxy…

  • Automation
  • Network Services
PlugNPiN scans labelled Docker containers and automatically creates local DNS records in Pi-hole or AdGuard Home plus matching Nginx Proxy Manager proxy hosts, saving self-hosters manual DNS and reverse-proxy setup.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • 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

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.

63/100 Good

Maintained
86last commit 6 days ago
Popular
3771 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
88no serious findings, 2 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
71
Open issues
2
Last commit
2026-11-15
Latest release
v1.0.1
License
GPL-3.0
Activity
rising

Checked 2 days ago - source: GitHub (deepspace2/plugnpin)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Container labels Flag services by labelling containers: plugNPiN.ip sets the container address (e.g. 192.168.1.100:8080) and plugNPiN.url sets the local domain name. Distant hosts can be included via a Docker socket proxy; Pi-hole is enabled by default while AdGuard Home starts disabled. source
  • Container labels and DNS defaults Label Docker containers for PlugNPiN to detect them. Pi-hole is enabled by default; AdGuard Home is disabled by default. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker labels must be added for PlugNPiN to detect a container?

Containers need plugNPiN.ip with the container IP and port, and plugNPiN.url with the desired local domain name. Multiple domains can be comma-separated in plugNPiN.url.

How should PlugNPiN access the Docker daemon securely?

Use a Docker socket proxy instead of giving the PlugNPiN container direct access to the Docker socket. The documented setup uses a socket-proxy service with CONTAINERS=1 to limit privileges.

How does PlugNPiN keep DNS and proxy settings synchronized?

It listens for Docker start, stop, and kill events to add or remove entries immediately. It also performs a full synchronization at a regular interval defined by RUN_INTERVAL to correct missed or inconsistent entries.

Which DNS backend is enabled by default?

Pi-hole is enabled by default, while AdGuard Home starts disabled.

Answers sourced from github.com, github.com

Community

Collected 2 days ago - public community threads