# PlugNPiN

PlugNPiN is a self-hosted automation app. 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.

Canonical page: https://ourlocalhost.com/app/8680/plugnpin

## Description

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: Any server.

## Health score

63/100 (Good), based on 4 of 5 factors.
- Maintained: 86 (last commit 6 days ago)
- Popular: 37 (71 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 88 (no serious findings, 2 minor, CI, tests)

## Links

- Official website: https://deepspace2.github.io/PlugNPiN
- GitHub: https://github.com/deepspace2/plugnpin

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/8680/plugnpin), the self-hosted and open-source app directory.
