From 5bf11d980aef9242f699a21cb21d2dd97b06a6b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ren=C3=A9=20Moser?= Date: Mon, 16 Sep 2019 23:38:31 +0200 Subject: [PATCH] Update README.md --- README.md | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 847087b..662631f 100644 --- a/README.md +++ b/README.md @@ -6,20 +6,27 @@ This is a fork of http://nip.io with some neat changes. Dead simple wildcard DNS for any IP Address -NIP.IO allows you to map any IP Address in the following DNS wildcard entries: +nip.io allows you to map any IP Address in the following DNS wildcard entries: +It works with Dashes `-`, perfect for wildcard TLS certs: ~~~ 10-0-0-1.nip.io maps to 10.0.0.1 -10.0.0.1.nip.io maps to 10.0.0.1 app.10-0-0-1.nip.io maps to 10.0.0.1 -app.10.0.0.1.nip.io maps to 10.0.0.1 customer1.app.10-0-0-1.nip.io maps to 10.0.0.1 -customer1.app.10.0.0.1.nip.io maps to 10.0.0.1 -otherapp.10-0-0-1.nip.io maps to 10.0.0.1 +~~~ +As well as Dot `.`: +~~~ +10.0.0.1.nip.io maps to 10.0.0.1 +app.10.0.0.1.nip.io maps to 10.0.0.1 +customer1.app.10.0.0.1.nip.io maps to 10.0.0.1 NIP.IO maps ..nip.io to the corresponding , even 127-0-0-1.nip.io maps to 127.0.0.1 ~~~ +See https://github.com/resmo/nip.io/blob/master/src/backend.conf.example for an example config + +**Hint**: See the static CNAME `_acme-challenge=xyz.auth.example.com.` in the example, use it with https://github.com/joohoi/acme-dns for free Let's Encrypt TLS certs. + ## INSTALL ### As docker container @@ -31,7 +38,7 @@ docker build -t nip.io . Run the container: ~~~ -docker run -d -p 0.0.0.0:53:53/tcp -p 0.0.0.0:53:53/udp --name nip.io nip.io +docker run -d -p 0.0.0.0:53:53/tcp -p 0.0.0.0:53:53/udp -v /data/backend.conf:/usr/local/bin/backend.conf --name nip.io nip.io ~~~ See the logs: