Is DNS Bloat too?

That's a cat who knows his networks
Why are catboys/girls and furries always the best at explaining stuff succinctly?? Lmao
- They run the internet now so they really know how it works.
- Maybe that skill is how they end up with suspiciously high amounts of money.
Holy crap, this ... This ... Is very accurate...
Thank you for this
At first I thought this was a joke, but it's actually informative 🤔
- Right? This was so educational!
Holy fuck I forgot about this video. Classic.

Tbh, if you can't tap out Ethernet frames with a Morse key and decode the response by watching the blinking of an LED wired to the RX pair then you really don't deserve to be on the internet. Git Gud.

Okey, I don't get it. What's wrong with DNS?

When it breaks, it isn't always obvious or easy to fix, but can cause problems for anything that has to talk to anything else. The biggest thorn it puts in my side is that short names [ThisPC] are served differently than fqdn [ThisPC.MyDomain.com]. Does NotMyApp use short or FQDN to resolve other machines? I don't find out until the Wireshark.
- Okey, I understand this is fundamental and when not working can cause the service to stop working. But I don't yet know how does it break or is not easy to troubleshoot?
  
  Haven't hosted anything big yet, so I always just had to check the records via "dig" command if they are served correctly.
https://old.lemmy.sdf.org/post/9808257
- Uh... Please enlighten me on what DBUS has to do with DNS...
- Is the fact that that link couldn't resolve your answer to that question haha?

I use pigeons and let the wind tell me where to send them.

CC BY-NC-SA 4.0

CC BY-NC-SA 4.0

This might be funnier than all those Facebook accounts with warnings about "I do not authorize anyone to use my photos!"

Because they're trying to copyright an internet comment that they posted on a service hosted by someone else, with a creative commons license attached. It's like a step up in knowing how shit works, but still not knowing enough.

If you really want ownership over what you say.... don't post it on the fucking internet.
- I mean, not really. You own the stuff you create regardless of who's hosting it. Microsoft doesn't own the copyright for the millions of projects hosted on GitHub either.
- Wait lol are people posting that to their comments to use it as claimed ownership? I did not realize that was the intent there
CC BY-NC-SA 4.0

Are you trying to... copyright your comment? IPoAC existed prior to your comment.
- It’s not even a license, just an abbreviation that people may, or may not, be familiar with.
- I really need a link to a blurb about the CC thing, but not today. Basically think AI.
  
  CC BY-NC-SA 4.0
There's an RFC for that
- TIL, thanks 😄
  
  CC BY-NC-SA 4.0

It's insecure, which lets governments like China poison it. They straight up block encrypted DNS

Lol ... DNS is one of the pillars upon which the internets tands, a crumbling mess of a pillar but I'm sure glad we don't have a name system built on hosts files 😹

My prediction is that we'll go DNSSEC globally when IPv6 gets mainstream adoption. It sucks how many just don't care enough.

when IPv6 gets mainstream adoption

At the current speed that would approximately be in 2087.
- Whoa there, let's not get ahead of ourselves.
when IPv6 gets mainstream adoption.

After my death then. Alright, carry on.
The abysmal adoption of DNSSEC is just embarrassing, and I haven’t heard any good arguments for why we shouldn’t do it. There’s one blog post that gets passed around as justification for not adopting DNSSEC, but it doesn’t really go into any technical detail and is mostly just the author saying “I’m scared of governments and TLDs”… which is maybe fair, but you still have to trust them for regular CA certs and everything, so why not make thr base secure?

Honestly, I might care slightly more about DNSSEC than IPv6 adoption… IPv4 exhaustion and NATing everywhere sucks, but the fact that you can’t trust DNS is like… insane.