If you can't remember the IP address of every site you'd like to visit, you don't deserve the internet.
Pro tip, You don't have to remember it. I have all my favorite IPs in a nice address book, keep it in my drawer next to my passwords
My company actually used a whiteboard instead of a DNS for our internal network. We used it as a temp solution during setup, then 5 years later it was still in use. It worked quite well.
Oh, you like the internet? Name every IP address!
0.0.0.0/0
Don't even get me started with IPv6!
::/0 ?
I know this one! All credit goes to FauxPseudo@lemmy.world
"^\s*((([0-9A-Fa-f]{1,4}:){7}([0-9A-Fa-f]{1,4}|:))|(([0-9A-Fa-f]{1,4}:){6}(:[0-9A-Fa-f]{1,4}|((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3})|:))|(([0-9A-Fa-f]{1,4}:){5}(((:[0-9A-Fa-f]{1,4}){1,2})|:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3})|:))|(([0-9A-Fa-f]{1,4}:){4}(((:[0-9A-Fa-f]{1,4}){1,3})|((:[0-9A-Fa-f]{1,4})?:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3}))|:))|(([0-9A-Fa-f]{1,4}:){3}(((:[0-9A-Fa-f]{1,4}){1,4})|((:[0-9A-Fa-f]{1,4}){0,2}:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3}))|:))|(([0-9A-Fa-f]{1,4}:){2}(((:[0-9A-Fa-f]{1,4}){1,5})|((:[0-9A-Fa-f]{1,4}){0,3}:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3}))|:))|(([0-9A-Fa-f]{1,4}:){1}(((:[0-9A-Fa-f]{1,4}){1,6})|((:[0-9A-Fa-f]{1,4}){0,4}:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3}))|:))|(:(((:[0-9A-Fa-f]{1,4}){1,7})|((:[0-9A-Fa-f]{1,4}){0,5}:((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])(\.(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9]?[0-9])){3}))|:)))(%.+)?\s*$"
That is a forkbomb and you can't convince me otherwise
i dare you to run it
127.0.0.1
Unironically, I used to remember 3.
2 for servers with internet radios and 1 for google. But I forgot. Except 149.13.0.82.
I remember 1 of the Google dns ones, only because when trouble shooting network issues it is my go to ip to ping so I know the instant I am connected again.
Oh, I forgot about DNS servers. Then I remember:
8.8.8.8 - Google
9.9.9.9 - Quad9
1.1.1.1 and 1.0.0.1 - Regular Cloudflare
1.1.1.2 and 1.0.0.2 - Cloudflare "Malware blocking"
1.1.1.3 and 1.0.0.3 - Cloudflare "Malware and adult content blocking"
45.90.30.180 and 45.90.28.180 - NextDNS
And I think 2960:fe::fe is also Quad9, but I'll have to check. Nope, it's 2620:fe::fe. So just the ones above.
DNS is hierarchical majesty.
That's a cat who knows his networks
Holy crap, this ... This ... Is very accurate...
Why are catboys/girls and furries always the best at explaining stuff succinctly?? Lmao
Thank you for this
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.
I use pigeons and let the wind tell me where to send them.
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.
I use pigeons and let the wind tell me where to send them.
So is other guy gonna sue me now and win because I just copy and pasted what they said? This is a joke.
I mean, probably not. That's such a short post, chances are courts wouldn't find it copyrightable. And obviously attaching a license at the end of your comments is useless in practice, because no one on the internet actually properly engages with copyright law. Plus suing over copy-pasting someone's social media post is dumb as hell and no one does that, tho I do think you could technically do it and win, because current copyright laws make zero sense if you actually stop and think about it for any amount of time.
current copyright laws make zero sense if you actually stop and think about it for any amount of time.
So true.
My lawyers will argue that this willful infringement of my rights as the orignal author of the famous 1997 Internet comment "So true" means that you now owe me $4000000 in damages, but I'll settle for one bitcoin.
And yet Microsoft made Copilot, and there are currently lots of clueless programmers out there using it to inject code with god knows what licenses into their company's software.
Which hasn't been free of legal challenges. Current copyright law doesn't account for machine learning, which is what allows them to do this. This could soon change.
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.
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.
I have no doubt in my mind that there's some subset of the suckless crowd that thinks dns is bloat
We should remove all those useless microservices! /s
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 😹
As we all know, it's always DNS.
It's insecure, which lets governments like China poison it. They straight up block encrypted DNS
@scroll_responsibly Laughing in my self-hosted services, on my VPS which use only IP address :blobcatjoy:
*Currently every service is also available via IPv6 :3
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
