sorted by: recent | see :
popular
Content Tagged with Server + HTTP
DNS Hijacking, ISP Packet Modification, Morals and Privacy
http://www.adamsinfo.com/dns-hijacking-isp-packet-modification-morals-and-privacy/#more-118
While looking at some data statistics for one of our racks, I noticed that the DNS service has become incredibly busy as of late. Now about 4 years ago when these particular name servers were set up, they were left with their default option to respond to DNS queries to anyone for anyone. It’s not really terrible but hardly ideal so I began changing some settings. I do notice though that we seem to now be providing name server access to the large majority of the world. Only recently did I read an article on DNS Hijacking that certain ISPs use to deliver pay per click ads to their subscribers when they do anything from first start their browser to each time they hit a DNS error.
Now personally I think it’s a pretty cheap thing to do, and it’s also quite frustrating to those users that have to suffer this ‘feature’. A number of ISPs use such methods to ‘improve’ the quality of your service and I think it’s all pretty bad. I don’t think there’s anything wrong with legitimate website ads in order to earn an author or site master some money – I’m going to put a few here sometime, however offensive advert popups or other nasty behavior are really not acceptable by anyones standards anymore.
Hijacking DNS queries, sniffing and modifying HTTP in any way, sniffing or modifying any kind of email or email failure, redirecting IPs, transparently proxying web traffic, analyzing your traffic, shaping your torrent-like or other rule matched traffic, etc, etc – you get the idea, are some of the more popular techniques out there. In worst cases an ISP would even firewall your inbound and outbound port access.
Bottom line, it’s not right. In a reasonable ‘open source’ mentality, an ISP should offer a clean, usable connection. They should not affect or modify your traffic in any way, seek to gain advertising from it or anything similar. If you mess about with end users connections, users usually end up complaining to site providers about something that isn’t their problem, and don’t get to understand what they’re doing and how or why their internet behaves differently to the next guy’s.
With that, I was confident that injecting ads for profit or otherwise messing about with my now-popular DNS service wasn’t a good thing to do, even if my subscribers shouldn’t have been subscribers :mrgreen: . I restricted access to the relevant ranges, and with that I was done.
Server
hijacking
DNS
HTTP
internet
source
open
and
privacy
User:davidapnic
