What stopping websites from directly linking to the ip address then? You don’t need a dns if the browser directly points to htttps://231.157.68.8 or whatever. domain names are just branding for fucks sake
Nobody is going to memorize IP addresses. If.you want people to shop at your dildo store, it is a.lot.easier to remember davesFatDildos.com vs an IP address.
If created a nice table of names mapped to IP addresses, then you just recreated dns, but worse.
Also, no DNS means no fault tolerance, cert problems, no effective load balancing, very hard to change providers, maintenance of.taking a host down is all but impossible.
There is a reason DNS exists. Thinking we could abandon it just demonstrates a lack of understanding regarding how it works.
Noone types a url anymore. They go to google and rype what they want
Nobody is going to memorize IP addresses. If.you want people to shop at your dildo store, it is a.lot.easier to remember davesFatDildos.com vs an IP address.
Hence my point that domain names are for branding.
taking a host down is all but impossible.
Yeah, that is my point. You can’t ‘take down’ an ip address (except through the obvious end point internet service provider)
The internet is just connecting IP addresses together. Everything you’re talking about has been added onto this fact since the first .com bubble build up in the 90s, which is a bunch of CORPORATE BULLSHIT meant to control the information of simply connecting peoples computers together.
Domain names are not just branding. They’re critical to the infrastructure behind most sites.
a “site” is just one computer sharing information with another. limited to the hyper text markup language. Why would a computer that is connected by its IP address need a host name to send html to your computer? It wouldn’t.
A lot has changed since 1999 friend.
Websites are potentially dozens of virtual computers running on a half dozen physical computers, spread across several regions or countries.
There are potentially dozens or even hundreds of IP addresses involved with just the one host name, which all of these components rely on to function.
In a simpler setup, I in one case have a computer with one IP address that hosts 20 different websites. If you send a request to the IP address your request will be dropped because it won’t know which of those 20 websites you’re trying to reach.
1 website being 1 computer reachable on 1 IP address isn’t something you see very often anymore.
Subdomain.domain.com might point to a different IP address. You might have systems in mission critical deployments that can’t be updated with new IP addresses but will still work if they point to the domain.
Does this not break TLS?
Only if they don’t have the ip in the cert
IP certs are quite hard to get, used to be basically impossible not too long ago.
Edit: Not so hard anymore. Letsencrypt added them this year (finally) with the normal http challenge and 6 day lifetime. Which should be fine in normal automated setups. Still not supported accross major acme providers but this’ll make it easy enough to do.
So TLS on bare IPs should be just fine now.
Many websites and web apps these days have hostname filtering at the webserver level. Even if the IP address from the client is correct, it will not permit a connection that way. The req needs to come with one of the valid hostnames in the header, inc the correct protocol. At least, that’s what I do with mine. The req must come with https://whatever/ or https://www.whatever/ or the req gets ignored completely.
If an intermediary such as CloudFlare is used, there’s likely to be another layer of req filtering at the CloudFlare level.
I imagine you could edit your hosts file, or connect to a nonstandard dns to get the correct host name behavior at least
ISPs could block access to those, too.
Honestly, some really good points being made here…
DNS resolver blocking is a blunt tool that strips away whole domains at a time, meaning all content is blocked - legal and illegal alike - and does so in a completely non-transparent way.
And it’s like redacting a single map. Not only could you just bypass the map if you know directly where you’re going, you could also just get another map of the same area!
All that running the big public DNS resolvers out of town does is push people towards lesser known resolvers that are much less transparent and accountable.
To your second paragraph. Not sure where I read it (I think the context was CP) but I found this comparison quite fitting: “Blocking DNS entries is fighting symptoms instead of fighting the disease, the servers with the material are still there.”
I see them as an additional security layer - known phishing site? Known malware site? Block them at the DNS level now and you have already several potential victims saved, while you go after them and take them down completely which might take some time (hours/days/weeks).
But that assumes that you actually try to do the second part…
Lesser known is not necessarily a bad thing. Part of the current problem with the internet is consolidation into fewer and fewer hands. We could do with more, not less. However the problem is to ensure they are trustworthy, as you mention.





