Show HN: Backname.io – every IP address gets its own domain

Nice. I&#x27;ve seen other usecases for this.<p>Accessing an IPv4 address on a IPv6-only network with NAT64&#x2F;DNS64 is only possible if you access that IPv4 via a DNS name that resolves to the IPv4 address. DNS64 will turn your A record into an AAAA record, with the IPv4 address mapped to a v6 addrsss that the NAT64 layer knows how to &quot;undo&quot;.<p>I&#x27;ve seen others need this a few times in practice.

The problem is someone ends up using one of these in production. Then backname.io becomes an attractive target.<p>It would be cool to have it as a locally installed custom DNS resolver on the developers computer though.

I&#x27;m failing to see the utility of this if I still have to type the IP address. Also, it fails using local address like 192-168-1-1.backname.io where it might be usefull somehow, so, please explain. Thanks.

xip.io was indeed useful. nip.io seems to still work.<p>Isn&#x27;t the main useful aspect that you can do xyz.1.2.3.4.backname.io where xyz is anything you want? Perhaps you set this up anyway, but would be worth mentioning.

There is also <a href="http:&#x2F;&#x2F;traefik.me&#x2F;" rel="nofollow noreferrer">http:&#x2F;&#x2F;traefik.me&#x2F;</a><p>There is <a href="https:&#x2F;&#x2F;ipq.co&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;ipq.co&#x2F;</a> and <a href="https:&#x2F;&#x2F;fdns.uk&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;fdns.uk&#x2F;</a> that will let you create a name to point to a chosen ip.

<a href="https:&#x2F;&#x2F;github.com&#x2F;ncruces&#x2F;keyless">https:&#x2F;&#x2F;github.com&#x2F;ncruces&#x2F;keyless</a> was my attempt to provide you with the necessary tools to build your own service that would not only:<p><pre><code> - give you a domain for any IP (even local IPs); - give you SSL on that domain (even local IPs!); - abide by Let&#x27;s Encrypt terms.</code></pre>

Does this serve the same purpose as .in-addr.arpa?

I can think of at least four reasons and security concerns not to use a service like this:<p>- Exposing a potentially private IP to an external service<p>- If testing local IPs, adds a requirement for an internet connection<p>- Must trust that it will always resolve to the actual IP not another one<p>- Requires your service to accept a hostname that it likely shouldn&#x27;t

Just by looking at the handler, it is not RFC compliant. I do not see SOA record being generated properly nor do I see a proper handling of nxdomain vs nodatae responses.<p>See RFC 2308.

&gt; 127-0-0-1.backname.io resolves to 127.0.0.1<p>Is this enough to fool Edge (Windows 10) into allowing you to view your local Apache development environment?

This is cool! So I can spin up a server, then instantly get a domain and then an SSL cert, nice!

<a href="http:&#x2F;&#x2F;afraid.org" rel="nofollow noreferrer">http:&#x2F;&#x2F;afraid.org</a>