DNS isn't a service (in the same way as AWS and CloudFlare). It's a fundamental component of the world wide web.
I mean, unless you'd rather type IP addresses in to your URLs, anyways.
this post was submitted on 19 Nov 2025
492 points (98.8% liked)
memes
18078 readers
1962 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
I mean, I do put in http://149.13.0.80/radio1hi.aac to listen to Radio 1. I also use it to test my network when DNS potentially screwed up.
I used to remember the domain name, then I did the IP for fun, now I only remember the IP. Perhaps I could do reverse lookup, but it's been working for quite a while now.
Aren’t IPs prone to change though?
If it does what’s stopping someone from somehow getting that IP and hosting a fraud site?
The same thing that stops people from getting access to your domain registration and changing the IP. You have a contract with your provider (ISP or DNS) which says that you own that IP/Hostname.
Your home IP address changes, but most business or commercial accounts are given a static IP address (or blocks of IP addresses) which never changes.
Comcast used to offer this for an extra $10/month to residential customers. Not anymore.
Yeah, I used it until they rolled it into the business accounts (which I upgraded to in order to dodge data caps and have a symmetrical connection, because bittorrent).
I think in this case it'd be the user not putting in any sensitive data or downloading executables to run from an internet radio.
Blaming DNS is sort of like blaming phone numbers for calls failing to route. The reason it fails so often is because it’s almost exclusively a human-made lookup table.
I'm divesting myself of all three!
Anyone know any open source alternatives to DNS???
Look at this noob! They don't even have all the IP addresses memorized!
I hear homing pigeons are pretty good at location lookup. Maybe that old IP-over-pigeon RFC is worth a second look?
The economy hit hard and most my homing pigeons are now homeless
Don't forget sneakernet! Bandwidth is only limited by how much storage you can carry and if you want lower latency just drive faster
It's not dns....
Except every time
We'll have a quadfecta next week when an incorrect BGP statement causes all internet traffic to route through a mom & pop ISP in a rural part of central Asia.
Maybe OP should go learn a thing or 2 on how it actually works.
I know a thing or two on how it actually works and I found the post funny. I know it doesn't make sense but it's still funny.
Edit: to clarify (because it seems like you missed this point?), it's about the recent downtime of AWS and of Cloudflare a few days later, each of which caused a huge portion of the internet to be inaccessible. The AWS downtime was caused by a DNS error (as ever), and I'm not sure about Cloudflare but it might be as well.
I’m not sure about Cloudflare but it might be as well.
Cloudflare was a chain of unfortunate events.
The TLDR is, a permission change caused a poorly written SQL query (without a properly filtering 'where' clause) to return a lot more data than normal. That data is used by an automated script to generate configuration files for the proxy services, because of the large return the configuration files were larger than normal (roughly 2x the size).
The service that uses these configuration files has pre-allocated memory to hold the configuration files and the larger config file exceeded that size. This case, of having a file too large for the memory space, was improperly handled (ironically but not literally ironically, it was written in Rust) resulting in a thread panic which terminated the service and resulted in the 5xx errors.
So, it's more similar to the Crowdstrike crash (bad config file and poor error handling in a critical component).
no🙂↔️
If they were the learnin' type, they wouldn't be here
Oh this is a good one haha, can't believe I missed it a few days ago
Azure is also in there