I write English / Escribo en Español.

Vidya / videojuegos. Internet. Cats / Gatos. Pizza. Nap / Siesta.

This user’s posts under CC-BY-NC-SA license. Ask me if you need a different permission.

  • 2 Posts
  • 111 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle













  • The only task of a DNS server is (or should be) to tell you how to get to a resource you’re looking for by name. So, the only thing that is going to be reallistically affected is your (initial) connection times. And – since this is c/selfhosted – if you are setting a decent DNS cache in your local network, that should be even less of an issue.

    The only borderline scenario that I could see feasible, since this is c/selfhosted , is that some software you are setting up that requires nanosecond DNS resolution or somesuch sillyness is going to fail or report false errors. But why would you even do that?








  • The attack surface yes, but not the attack volume. No matter if the app is containerized or native, it has access to the data that it has to operate to. That’s literally part of computer nature.

    But a containerized app, assuming the container service itself is kept up to date, has less hooks to break into other stuff than a native app does. For starters, a native app can read everything that’s world-readable, which in a shared system might be lots of stuff but in a containerized app might be quite minimal.