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…

  • Network Services
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

  • 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 (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.

26/100 Low

Maintained
0GitHub repository is archived
Popular
3877 GitHub stars
Easy to install
150 install platforms, install notes
Light to run
No data
Security check
75no serious findings

Based on 4 of 5 factors.

GitHub stars
77
Open issues
11
Last commit
2026-09-23
License
GPL-2.0
Activity
stale

Checked 3 days ago - source: GitHub (coppit/docker-no-ip)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Retired project The repository README marks this project as retired and points new users to the official No-IP Docker image instead. source
  • Configuration Run the container with USERNAME, PASSWORD, DOMAINS, and INTERVAL environment variables, or mount a config file, to authenticate and schedule updates. source
  • Container configuration Set USERNAME, PASSWORD, DOMAINS, and INTERVAL as environment variables, or mount a config file at /config. source
  • Use the official No-IP image This project is retired; run the official No-IP Docker image instead. The linked No-IP knowledge base article has the run command and required credentials (username, password, domains, interval). source
  • Retired image usage The old coppit/no-ip image expected USERNAME, PASSWORD, DOMAINS, and INTERVAL environment variables or a config file. source
  • Retired image configuration For the coppit/no-ip image, set USERNAME, PASSWORD, DOMAINS, and INTERVAL, or use a config file. source

Fetched 4 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com, www.noip.com, www.reddit.com

Community

Collected 49 days ago - public community threads