Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I've never really understood the whole TTL thing. Will the domain essentially point to nothing if the TTL runs out while the DNS server is down or will it default to older record?
EDIT: also, I was unaware that you could strait bypass domain registrars and deal directly with the TLD owners...
The record will expire and, in this scenario, effectively become non-existent.
Once upon a time TTLs we’re rather long so temporary outages were less impactive. These days TTLs of less than a minute are common to accommodate redundancy. It doesn’t do want good to have redundant systems if DNS keep pointing at the downed system during an outage.
If the TTL runs out and is unable to reach an authoritative NS, it will yield an error saying that it cannot resolve the domain. If the library catalog is down, you know the book you want is there, you just don't know the location.
I didn't intend to imply that you can deal directly with the TLD. You could, theoretically, but they typically don't have the organization to dream with individual registrants. That's the job of registrars, who interface through their own software that does calls to the TLD's APIs.
It will most likely point to nothing. DNS servers can have performance improvements of sending the stale data while fetching it from the main source in order to be quicker, even though this is technically not correct. But in many cases the associated IP will not have changed anyway.
It depends on the implementation and configuration of the resolver you're asking. RFC 8767 allows serving stale data, if the TTL has expired but new data cannot be fetched.