this post was submitted on 09 Feb 2024
825 points (99.0% liked)

Programmer Humor

18961 readers
1370 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
all 40 comments
sorted by: hot top controversial new old
[–] [email protected] 89 points 6 months ago (1 children)
[–] [email protected] 7 points 6 months ago

Is it working? -> (Yes) --> Fix DNS

[–] [email protected] 43 points 6 months ago (6 children)

Does anyone else have the thought that maybe it's time to just replace these 30+ year old ancient protocols? Seems like the entire networking stack is held together with string and duct tape and unnecessarily complicated.

A lot of the decisions made sense somewhat in the 80s and 90s, but seems ridiculous in this day and age lmao

[–] [email protected] 87 points 6 months ago* (last edited 6 months ago) (3 children)

Seems like the entire networking stack is held together with string and duct tape and unnecessarily complicated.

The more you learn about network technology the more you realize how cobbled together it all is. Old, temporary fixes become permanent standards as new fixes are written on top of them. Apache, which was the most widely used web server for a long time, is literally named that because it was "a patchy" server. It's amazing that any of it works at all. It's even more amazing that it's been developed to the point where people with no technical training can use it.

The open nature of IP is what allows such a varied conglomerate of devices to share information with each other, but it also allows for very haphazard connections. The first modems were just an abuse of the existing voice phone network. The internet is a functional example of building the airplane while you're flying it. We try to revise the standards as we go, but we can't shut the whole thing down and rebuild it from scratch. There are no green fields.

It has always been so. It must be so. It will continue to be so.

(the flexibility of it all is really amazing though - in 2009 phreakmonkey was able to connect a laptop to the internet with a 1964 Livermore Data Systems Model A acoustic coupler modem and access Wikipedia!)

[–] TheMadIrishman 15 points 6 months ago

Nothing quite as permanent as a temporary fix!

[–] [email protected] 4 points 6 months ago

Very cool post, thanks for sharing

[–] [email protected] 30 points 6 months ago (1 children)

Some ancient protocols get replaced gradually though. Look at http3 not using TCP anymore. I mean at least it's something.

[–] [email protected] 2 points 6 months ago (1 children)

HTTP3 uses UDP, which is 6 years younger than TCP.

[–] [email protected] 3 points 6 months ago

Nope, it uses a protocol on top of UDP called QUIC. If you count underlying protocols further down the stack, obviously all of them are really old.

[–] [email protected] 21 points 6 months ago (1 children)

Wait till you hear about when ipv6 was first introduced (90s) and how 50% of the internet still doesn't work with it.

Businesses don't want to change shit that "works" so you still have stuff like the original KAME project code floating around from the 90s.

[–] [email protected] 1 points 6 months ago

Data Link layer be pretty stable to be fair ^_^

[–] [email protected] 19 points 6 months ago

I definitely would love to see a rework of the network stack at large but idk how you'd do it without an insane amount of cooperation among tech giants which seems sort of impossible

[–] [email protected] 13 points 6 months ago (1 children)

I may be waaaay off here, but the internet as it exists is pretty much built on DNS, isn't it? I mean, the whole idea of DARPANet back in the 60s and 70s was to build a robust, redundant, and self-healing network to survive nuclear armageddon, and except when humans f it up (intentional or otherwise), it generally does what it says on the tin.

Now, there's arguments to beade about securing the protocol, but to rip and replace the routing protocols, I think you'd have to call it something other than the Internet.

[–] [email protected] 10 points 6 months ago

Making a typo in the BGP config is the internet's version of nuclear Armageddon

[–] [email protected] 5 points 6 months ago

Same unfortunately goes for a big chunk of the law on a global scale.. Constant progress, new possibilities and technologies, changes in general are really outpacing some dusted and constantly abused solutions. Every second goes by and any “somehow still holding” relic is under more pressure. As a species we can have some really great ideas but the long-term planning or future-proofing is still not our strongest suit.

[–] [email protected] 33 points 6 months ago (1 children)

Me last week when my pi-hole was down

[–] [email protected] 3 points 6 months ago

Oh dang, I need to rebuild that one as well by chance. Still running on Buster...

[–] xmunk 25 points 6 months ago

Why do Canadians make such good network engineers?

We always make sure to check the Eh Record.

[–] [email protected] 19 points 6 months ago (1 children)

Literally this, literally today.

[–] [email protected] 10 points 6 months ago (1 children)

Same here, quite literally this morning, it was fucking DNS

[–] [email protected] 2 points 6 months ago

Those little bastards, so sneaky. I've checked if d(uck)dns is working before my local DNS.

[–] [email protected] 18 points 6 months ago (1 children)

Am I the only one who can't think of a time DNS has caused a production outage on a platform I worked on?

Lots of other problems over the years, but never DNS.

[–] [email protected] 16 points 6 months ago (1 children)

I have a coworker who always forgets TTL is a thing, and never plans ahead. On multiple occasions they've moved a database, updated DNS to reflect the change, and are confused why everything is broken for 10-20 minutes.

I really wish the first time they learned, but every once and a while they come to me to troubleshoot the same issue.

[–] [email protected] 2 points 6 months ago (2 children)

Set it to 5 seconds ??? Profit

[–] [email protected] 5 points 6 months ago

??? Is when the underwear gnomes send you a massive bill because you're paying per 1k lookups. They profit, you don't

[–] [email protected] 3 points 6 months ago

"yes boss we need another 20 dns servers" "idk why dns traffic is so heavy these days"

[–] [email protected] 14 points 6 months ago

The problem is the cache. Always.

[–] [email protected] 14 points 6 months ago

For real, I've had problems where I specifically checked if it was DNS, concluded it was not, but it still turned out to be DNS.

[–] [email protected] 6 points 6 months ago

Actually while for myself it is sometimes DNS, if I see an internet wide outage it's usually BGP.

[–] [email protected] 6 points 6 months ago (2 children)

I feel like there's some context here I'm missing...

[–] [email protected] 14 points 6 months ago

Networking issues are very often caused by DNS, even in cases which don't initially look DNS related at all.

[–] [email protected] 3 points 6 months ago

It's a haiku about network issues

[–] [email protected] 4 points 6 months ago

No words describe such 🤌

[–] [email protected] 4 points 6 months ago

Nice painting!

[–] [email protected] 3 points 6 months ago

Not uncommon.