| ▲ | pas 4 days ago | |
you went from 10USD to thousands in a few sentences. self-hosting has a lot of degrees. if you want your own TLD and peer with Tier1s, then it's astronomical, woo! But using dynDNS is also an option. Especially if you compare to non-self-hosted services. You get a subdomain and that's it. (Or nothing, maybe some handle on Instagram.) | ||
| ▲ | spauldo 3 days ago | parent [-] | |
I have a .net domain that used to point to the nameserver at my house. It works fine, although if your IP changes you have to update your glue records and whatnot. You can get free secondary DNS service from a several places. All I paid was the cost of the domain registration. These days I have a Debian instance running at DigitalOcean that costs me $6/mo that acts as my primary DNS, with my home server as the secondary. I'm paying more, but I use that Debian instance for a few other things as well so I don't mind. The major benefit is I no longer worry about my IP changing at home, but it's not absolutely necessary. | ||