zishuo/nip
1
0
Fork 0
mirror of https://github.com/cunnie/sslip.io.git synced 2025-10-07 00:23:44 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Web page: use sslip.io servers, not nono.io

Browse Source
This commit is contained in:
Brian Cunnie
2021-11-27 18:23:02 -08:00
parent 690e0ad618
commit 7ed2107f36
1 changed files with 17 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
k8s/document_root/index.html
View File

@@ -113,9 +113,10 @@ src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> <![endif]-->
own the domain “example.com”, and you want your subdomain, “xip.example.com” to have xip.io-style features. To
accomplish this, set the following three DNS servers as NS records for the subdomain “xip.example.com”</p>
<div class="alert alert-warning" role="alert">
<b>2019-07-31 Nameserver (NS) Change!</b> Update your nameservers. We have deprecated ns-vultr.nono.io because
it's turned off the last week of the month when it has reached its 3 TB bandwidth quota. On 2018-09-20 we
deprecated ns-he-nono.io.
2021-11-27 For your information, we've switched to using our own nameservers (sslip.io) instead of the old
nono.io nameservers. Don't worry if you're pointing to the old nameservers—they'll continue to work properly.
In fact, under the hood they are the same nameservers; the change is merely cosmetic: we've created sslip.io
DNS records for them.
</div>
<table class="table">
<thead>
@@ -127,25 +128,25 @@ src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> <![endif]-->
</thead>
<tbody>
<tr class="odd">
<td><code>ns-aws.nono.io.</code></td>
<td><code>ns-aws.sslip.io.</code></td>
<td>52.0.56.137<br>
2600:1f18:aaf:6900::a</td>
<td>USA</td>
</tr>
<tr class="even">
<td><code>ns-gce.nono.io.</code></td>
<td><code>ns-gce.sslip.io.</code></td>
<td>104.155.144.4</td>
<td>USA</td>
</tr>
<tr class="odd">
<td><code>ns-azure.nono.io.</code></td>
<td><code>ns-azure.sslip.io.</code></td>
<td>52.187.42.158</td>
<td>Singapore</td>
</tr>
</tbody>
</table>
<p>Let’s test it from the command line using <code>dig</code>:</p>
<pre><code>dig @ns-gce.nono.io. 169-254-169-254.xip.example.com +short</code></pre>
<pre><code>dig @ns-gce.sslip.io. 169-254-169-254.xip.example.com +short</code></pre>
<p>Yields, hopefully: <sup><a href="#timeout" class="alert-link">[connection timed out]</a></sup></p>
<pre><code>169.254.169.254</code></pre>
<h3 id="server">But I Want My Own DNS Server!</h3>
@@ -188,16 +189,16 @@ dig @localhost 127-0-0-1.sslip.io +short # returns "127.0.0.1"</pre>
<h3 id="experimental">Experimental Features</h3>
<p>Experimental features can change; don't depend on them.</p>
<h4 id="whatismyip">Determining Your External IP Address via DNS Lookup</h4>
<p>You can use sslip.io's DNS servers (<code>ns-aws.nono.io</code>, <code>ns-azure.nono.io</code>,
<code>ns-gce.nono.io</code>) to determine your public IP address by querying the <code>TXT</code> record of
<p>You can use sslip.io's DNS servers (<code>ns-aws.sslip.io</code>, <code>ns-azure.sslip.io</code>,
<code>ns-gce.sslip.io</code>) to determine your public IP address by querying the <code>TXT</code> record of
<code>ip.sslip.io</code>. If you're curious about your public IPv6 address, use the DNS server
<code>ns-aws.nono.io</code>, for it has both IPv4 and IPv6 addresses:</p>
<code>ns-aws.sslip.io</code>, for it has both IPv4 and IPv6 addresses:</p>
<pre>
dig @ns-aws.nono.io txt ip.sslip.io +short # sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"
dig @ns-aws.nono.io txt ip.sslip.io +short -4 # forces IPv4 lookup; sample reply "172.58.35.231"
dig @ns-aws.nono.io txt ip.sslip.io +short -6 # forces IPv6 lookup; sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"</pre>
dig @ns-aws.sslip.io txt ip.sslip.io +short # sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"
dig @ns-aws.sslip.io txt ip.sslip.io +short -4 # forces IPv4 lookup; sample reply "172.58.35.231"
dig @ns-aws.sslip.io txt ip.sslip.io +short -6 # forces IPv6 lookup; sample reply "2607:fb90:464:ae1e:ed60:29c:884c:4b52"</pre>
<div class="alert alert-warning" role="alert">
When querying for your IP address, always <b>include the sslip.io nameserver</b> (e.g. <i>@ns-aws.nono.io</i>).
When querying for your IP address, always <b>include the sslip.io nameserver</b> (e.g. <i>@ns-aws.sslip.io</i>).
If omitted, you won't get your IP address; instead, you'll get the IP address of your upstream nameserver.
</div>
<p>This feature was inspired by Google's DNS lookup, i.e. <code>dig txt o-o.myaddr.l.google.com @8.8.8.8
@@ -224,14 +225,14 @@ dig @ns-aws.nono.io txt ip.sslip.io +short -6 # forces IPv6 lookup; sample reply
</li>
</ul>
<p>A big advantage of using DNS queries instead of HTTP queries is bandwidth: querying
<code>ns-aws.nono.io</code> requires a mere 592 bytes spread over 2 packets; Querying <a href=
<code>ns-aws.sslip.io</code> requires a mere 592 bytes spread over 2 packets; Querying <a href=
"https://icanhazip.com/">https://icanhazip.com/</a> requires 8692 bytes spread out over 34 packets—over 14 times
as much! Admittedly bandwidth usage is a bigger concern for the one hosting the service than the one using the
service.</p>
<h4 id="version">Determining The Server Version of Software</h4>You can determine the server version of the
sslip.io software by querying the TXT record of <code>version.sslip.io</code>:
<pre>
dig @ns-aws.nono.io txt version.sslip.io +short
dig @ns-aws.sslip.io txt version.sslip.io +short
"2.2.3"
"2021/11/27-11:35:50-0800"
"074f0a8"