[Discussion] New DNS Pointing

I believe it’s an opportune moment to revisit this project after five years of its successful run, especially considering the recent issue raised on GitHub (https://github.com/Upinel/localhost.direct/issues/18).

Back in 2019, localhost.direct was a simple yet elegant project that shared my keys and domain with the developers’ community. Over the past five years, I’ve personally been using a different domain name (top secret) with the same purpose: local development with SSL certificates. I’ve refrained from making any changes to localhost.direct since it’s been stable, and the adage “When things are stable, DON’T touch it” holds true.

However, as I embark on this project review, I’m eager to understand the community’s vision for localhost.direct. One idea that has been percolating in my mind is to introduce more pointing options using uncommon subdomains.

For instance, we could set up 10-0-0-1\~10.localhost.direct to point to 10.0.0.1\~10, and 192-168-0-1\~10 to point to 192.168.0.1\~10. This would enable users to install SSL certificates on their routers, NAS devices, and other equipment as long as they’re assigned the IP addresses listed in our resolve list. While I believe this approach has both advantages and disadvantages, I’m concerned about the potential impact on the community’s usage of localhost.direct. Unlike my personal domains, I don’t want to make arbitrary changes to the domain settings on localhost.direct since it’s a shared resource.

Therefore, I believe it’s important to have everyone’s input to guide the future direction of this project.

~Upinel

Upinel / localhost.direct

[Discussion] New DNS Pointing #21