PlugNPiN

Automatically scrapes containers with specific labels and creates local DNS/CNAME entries in Pi-Hole/AdGuard Home and proxy hosts in Nginx Proxy Manager.

Slowing · 38
38/100
Slowing

Activity has dropped noticeably. Check the repository before committing to it.

Maintenance 3/40
Releases 21/25
Community 1/20
Momentum 13/15

Commit activity more than 7% of tracked projects; popularity more than 5%. How this is calculated.

Commits, last 11 months

2025-10: 0 commits 2025-11: 0 commits 2025-12: 0 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 0 commits 2026-05: 0 commits 2026-06: 9 commits 2026-07: 5 commits 2026-08: 0 commits
2025-10 14 total 2026-08
Stars70
Latest releasev1.0.0 · 7 Jul 2026
Repo updated9 Jul 2026
LicenceGPL-3.0
Built withDocker

Is PlugNPiN actively maintained?

Development is ongoing. The repository recorded 14 commits over the same window, and the last three months alone account for 14 of them.

The most recent tagged release, v1.0.0, is about 3 months old.

PlugNPiN ranks #9 of 11 tracked network utilities projects. Several better-maintained options exist in the same category — they are listed below.

What PlugNPiN actually does

PlugNPiN is a Docker-based utility that automates local network configuration by scraping container labels. It generates corresponding DNS entries in Pi-Hole or AdGuard Home alongside proxy hosts within Nginx Proxy Manager.

Best fit: Home lab operators running Docker who want to automate the process of creating local DNS records and reverse proxy routing without manual intervention.

Worth knowing: The project has a relatively small community footprint and a slowing development pace, which may impact long-term maintenance and bug fixes.

Deployment notes

As a Docker container, it typically requires network access to your DNS sinkhole and proxy manager APIs, along with persistent storage if state is retained.


PlugNPiN as a replacement for


Alternatives to PlugNPiN

Projects in the same categories, ordered by health score.