8

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?

top 5 comments
sorted by: hot top controversial new old
[-] stown@sedd.it 2 points 1 year ago

If the DNS server for your Domain goes down the records should still be saved in all the other DNS servers around the world. They will stay the same as they were before you domain's DNS server wen't down. While your DNS server is down you won't be able to change where the Domain points. While your registration server is down you will not be able to transfer or sell your domain.

[-] Hyacin@lemmy.ca 1 points 1 year ago

Correct, but not the whole story.

If your registrar goes down, and you have your authoritative DNS anywhere else, then literally nothing happens. They just register the domain for you and give you an interface to pass your 'glue' records up to the TLD root servers.

If those glue records point to on-site DNS, or anything that is not your registrar's DNS servers, then your registrar being down is inconsequential other than that you would not be able to update your glue records, or renew your domain.

A separate question of "what happens if my authoritative servers go down", is answered above.

The two are not one in the same, though they can be.

[-] vegivamp@feddit.nl 0 points 1 year ago

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.

[-] stown@sedd.it 1 points 1 year ago

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?

[-] vegivamp@feddit.nl 1 points 1 year ago

Your domain is "hosted" (in this context, the DNS entries, not the actual content) on one or, ideally, more DNS servers that are known as the authoritative servers for your domain. You can look those up by searching the SOA (start of authority) and NS (nameserver) records for it.

Downstream servers may keep those and other records in cache for a while, usually guided by the TTL (time to live) entry. Once that expires, however, they need to refresh the data from the authoritative servers.

When those are unreachable, that cannot do so, and your domain is de facto unreachable for the internet at large, regardless of your own server actually being up.

You can still reach them by surfing to the actual IP instead, and/or hardcoding the DNS name in your local hosts file or your local DNS server/resolver. That is, of course, not visible to the internet at large.

You could host your own DNS servers to mitigate somewhat, but keep in mind that every level above your domain also needs to know which server is authoritative - my tuxera.be used to be self hosted, so the .be root servers had to know what the SOA for tuxera was.

Honestly, it's not something to worry about. I didn't keep up with changes in DNS security, so i switched to route53 (Amazon). I've been considering switching again to hetzner.de where i have some servers anyway.

DNS is pretty lightweight (relatively speaking), so it's probably the last thing to go down if a registrar is in trouble; you'd have plenty of warning signs beforehand.

(Yes, for pedantry, technically a registrar doesn't even have to offer DNS at all, they just handle ownership and administration at the top level domain, but most do anyway)

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

Selfhosted

39251 readers
209 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 1 year ago
MODERATORS