this post was submitted on 20 Jun 2023
29 points (100.0% liked)

Selfhosted

40895 readers
1004 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

If you register a domain with Cloudflare or Route 53, and that service goes down, do your records stay active in the DNS servers? What if the DNS servers go down, I know a lot of people use 8.8.8.8, so if Google's server goes down, then DNS fails?

What are the potential point of failures for having your own domain?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 2 years ago (1 children)

You should actually be able to transfer and sell - that's handled at the tld.

Also, there's a lifetime to that cache, so if it's down long enough it'll become unreachable.

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (4 children)

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...

[–] [email protected] 3 points 2 years ago

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.

[–] [email protected] 1 points 2 years ago

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.

[–] [email protected] 1 points 2 years ago

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.

[–] SheeEttin 1 points 2 years ago

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.