You are viewing a single comment's thread.

view the rest of the comments →

0
2

[–] ADaniels 0 points 2 points (+2|-0) ago 

Direct IP baby, DNS can suck my balls!

0
0

[–] crazy_eyes ago 

why the hell not?

0
3

[–] ghost_of_aswartz 0 points 3 points (+3|-0) ago  (edited ago)

Because many services ban directly connecting to IP, primarily because they are using distributed systems / load balancing or VPS hosted on a big service so they can take advantage of the wide pipe (bandwidth) that the colocation facilities have

There may be other reasons also, like for instance, FORCING you to use DNS (which I suspect)

The reason to force you to use DNS is to create a log of each and every website and each and every http / https request you make in order to track you.

That is why some have pushed DNScrypt and DNSsec, but they aren't widely availalbe and btw I speak as an expert on the subject (linux admin who has experience with this), it works beautifully until suddenly it doesn't and your whole dns traffic is hijacked by a man in the middle dns attack so that you cannot reach ANYTHING for a certain amount of time (I call it being given a DNS 'timeout', like a bad little kid). They are somehow able to do this at an upstream provider level (who your local isp gets their internet from);

They do this--I believe (and this is speculation and conspiracy theory now) to keep you from using encrypted DNS, because they want to track you

It has the same pattern and practice of the kind of harassment that patriots get from using a VPN software