# NoIp

NoIp is a retired Docker container for homelab users that keeps a No-IP hostname in sync with a changing home IP address; use the official No-IP Docker image instead. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/5891/noip

## Description

NoIp is a retired Docker container for homelab users that keeps a No-IP hostname in sync with a changing home IP address; use the official No-IP Docker image instead.

## Platform availability

Available on 0 of 10 platforms.

## Health score

26/100 (Low), based on 4 of 5 factors.
- Maintained: 0 (GitHub repository is archived)
- Popular: 38 (77 GitHub stars)
- Easy to install: 15 (0 install platforms, install notes)
- Security check: 75 (no serious findings)

## Links

- GitHub: https://github.com/coppit/docker-no-ip
- Docker Hub: https://hub.docker.com/r/coppit/no-ip
- Documentation: https://www.noip.com/support/knowledgebase/ip-linux-duc-docker

## Common questions

### How do I run the official No-IP DUC Docker container?

Pull the official noip-duc container, create an .env file with NOIP_USERNAME, NOIP_PASSWORD, and NOIP_HOSTNAMES, then run the container with docker run using the .env file.

### How was the older coppit/no-ip container configured?

It could be run with USERNAME, PASSWORD, DOMAINS, and INTERVAL environment variables, or by mounting a config directory and editing noip.conf.

### Do personal domains require extra No-IP DNS management for dynamic updates?

One self-hoster found that a personal domain required No-IP Plus Managed DNS for the IP address to update correctly.

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