From 4a50ebafd06fc46bde75d4fc459d372781549271 Mon Sep 17 00:00:00 2001 From: Brian Cunnie Date: Mon, 21 Jul 2025 06:55:57 -0700 Subject: [PATCH] Expand use of nip.io in README `nip.io` is a better domain name, shorter and more apropos (the "ssl" of "sslip.io" has long since lost its relevance), so I use more examples of nip.io. Signed-off-by: Brian Cunnie --- k8s/document_root_sslip.io/index.html | 57 +++++++++++++-------------- 1 file changed, 28 insertions(+), 29 deletions(-) diff --git a/k8s/document_root_sslip.io/index.html b/k8s/document_root_sslip.io/index.html index ab263c6..c60ff13 100644 --- a/k8s/document_root_sslip.io/index.html +++ b/k8s/document_root_sslip.io/index.html @@ -141,7 +141,7 @@ curl -L https://github.com/cunnie/sslip.io/releases/download/3.2.7/sslip.io-dns- chmod +x dns-server ./dns-server 2> dns-server.log & dnf install -y bind-utils -dig @localhost 127-0-0-1.sslip.io +short # returns "127.0.0.1" +dig @localhost 127-0-0-1.nip.io +short # returns "127.0.0.1"

TLS

You can acquire TLS certificates for your externally-accessible hosts from certificate authorities (CAs) such as Let's Encrypt. The easiest mechanism to acquire a certificate would be to use the minimum, a web server running on your machine. The Caddy web server is one of the most popular examples. For example, if you had a webserver with the IP address 52.0.56.137, you could - obtain a TLS certificate for "52.0.56.137.sslip.io", or "www.52.0.56.137.sslip.io", or - "prod.www-52-0-56-137.sslip.io".

+ obtain a TLS certificate for "52.0.56.137.nip.io", or "www.52.0.56.137.nip.io", or + "prod.www-52-0-56-137.nip.io".

-

If you have procured a wildcard certificate for your branded / white label / custom sslip.io-style subdomain, +

If you have procured a wildcard certificate for your branded / white label / custom nip.io-style subdomain, you may install it on your machines for TLS-verified connections.

-

When using a TLS wildcard certificate in conjunction with your branded sslip.io style subdomain, you must +

When using a TLS wildcard certificate in conjunction with your branded nip.io style subdomain, you must use dashes not dots as separators. For example, if you have the TLS certificate for *.xip.example.com, you could browse to https://www-52-0-56-137.xip.example.com/ but not https://www.52.0.56.137.xip.example.com/.

-

if you're interested in acquiring a wildcard certificate for your sslip.io domain, e.g. - "*.52-0-56-137.sslip.io", the procedure is described if you're interested in acquiring a wildcard certificate for your nip.io domain, e.g. + "*.52-0-56-137.nip.io", the procedure is described here.

Experimental Features

Experimental features can change; don't depend on them.

@@ -180,7 +180,7 @@ dig @ns.sslip.io txt ip.sslip.io +short # sample reply "2607:fb90:464:ae1e:ed dig @ns.sslip.io txt ip.sslip.io +short -4 # forces IPv4 lookup; sample reply "172.58.35.231" dig @ns.sslip.io txt ip.sslip.io +short -6 # forces IPv6 lookup; sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"

This feature was inspired by Google's DNS lookup, i.e. dig txt o-o.myaddr.l.google.com @8.8.8.8 @@ -214,22 +214,22 @@ dig @ns.sslip.io txt ip.sslip.io +short -6 # forces IPv6 lookup; sample reply "2 service.

Determining The Server Version of Software

You can determine the server version of the - sslip.io software by querying the TXT record of version.status.sslip.io: + nip.io software by querying the TXT record of version.status.nip.io: 
-dig @ns-ovh.nono.io version.status.sslip.io txt +short
-  "2.7.0"
-  "2023/10/04-18:51:49-0700"
-  "8f7f2df"
+dig @ns-ovh.sslip.io version.status.nip.io txt +short
+  "4.1.0"
+  "2025/06/22-17:49:11-0700"
+  "b879e43"
-

The first number, ("2.6.1"), is the version of the sslip.io DNS software, and is most relevant. The other two +

The first number, ("4.1.0"), is the version of the nip.io DNS software, and is most relevant. The other two numbers are the date compiled and the most recent git hash, but those values can differ across servers due to the manner in which the software is deployed.

Server Metrics

You can retrieve metrics from a given server by querying the TXT records of - metrics.status.sslip.io + metrics.status.nip.io 
-dig @ns-ovh.sslip.io metrics.status.sslip.io txt +short
-  "Uptime: 165655"
+  dig @ns-ovh.sslip.io metrics.status.nip.io txt +short
+    "Uptime: 165655"
   "Blocklist: 2023-10-04 07:37:50-07 3,6"
   "Queries: 14295231 (86.3/s)"
   "TCP/UDP: 5231/14290000"
@@ -266,23 +266,23 @@ dig @ns-ovh.sslip.io metrics.status.sslip.io txt +short
           that the number of responses with an answer record is typically a fourth the size of the overall responses.
           This is normal. One reason for this disparity is that often both the IPv4 (A) and IPv6 (AAAA) records will be
           checked, but only one reply will have a record in the answer section . For example, browsing to
-          "127.0.0.1.sslip.io" generates two lookups, one with an answer (IPv4), and one without (IPv6). Another reason
-          is that lookups follow a chain, e.g. looking up "127.0.0.1.sslip.io" may generate up to four queries for A
-          records ("1.sslip.io", "0.1.sslip.io", "0.0.1.sslip.io" and "127.0.0.1.sslip.io"), only the last of which
+          "127.0.0.1.nip.io" generates two lookups, one with an answer (IPv4), and one without (IPv6). Another reason
+          is that lookups follow a chain, e.g. looking up "127.0.0.1.nip.io" may generate up to four queries for A
+          records ("1.nip.io", "0.1.nip.io", "0.0.1.nip.io" and "127.0.0.1.nip.io"), only the last of which
           returns a record in the answer section. Pro-tip: if you want to shave milliseconds off name resolution, use
-          dashes not dots in your hostname (e.g. "10-9-9-30.sslip.io" instead of "10.9.9.30.sslip.io")
+          dashes not dots in your hostname (e.g. "10-9-9-30.nip.io" instead of "10.9.9.30.nip.io")
         
A

         
The number of responses which included an A (IPv4) record in the answer section since starting operation
-          (e.g. "dig 127.0.0.1.sslip.io")

+          (e.g. "dig 127.0.0.1.nip.io")
         
AAAA

         
The number of responses which included an AAAA (IPv6) record in the answer section since starting operation
-          (e.g. "dig --1.sslip.io aaaa")

+          (e.g. "dig --1.nip.io aaaa")
         
TXT Source

         
The number of responses which included a TXT record of the querier's IP address since starting operation
-          (e.g. "dig @ns.sslip.io ip.sslip.io txt")

+          (e.g. "dig @ns.nip.io ip.nip.io txt")
         
TXT Version

         
The number of responses which included a TXT record of the DNS's servers version since starting operation
-          (e.g. "dig @ns-hetzner.sslip.io version.status.sslip.io txt")

+          (e.g. "dig @ns-hetzner.sslip.io version.status.nip.io txt")
         
PTR IPv4/IPv6

         
This consists of two numbers; the first is the number of responses to IPv4 PTR queries
           (1.0.0.127.in-addr.arpa. → 127-0-0-1.sslip.io.), the second, IPv6 PTR queries

@@ -291,11 +291,11 @@ dig @ns-ovh.sslip.io metrics.status.sslip.io txt +short
           authority's DNS-01 challenge. This lookup is used for generating wildcard certificates from Let's Encrypt and
           other certificate authority. Technically this is not a "successful" query in that we don't return a record in
           the ANSWER section, but we do return an NS record in the AUTHORITY section. (e.g. "dig @ns-ovh.sslip.io
-          _acme-challenge.192.168.0.1.sslip.io. soa")
+          _acme-challenge.192.168.0.1.nip.io. soa")