I fought my ISP's bad behavior and won

#1

Post by helfire » Tue, Dec 31, 2013, 9:18 PM UTC

I fought my ISP's bad behavior and won
erichelgeson.github.io

Re: I fought my ISP's bad behavior and won

#2

Post by JoshTriplett » Tue, Dec 31, 2013, 9:55 PM UTC

Very nicely done: reporting this as abuse to the companies offering these affiliate programs seems quite appropriate, and it sounds like they reacted appropriately. One person complaining to an ISP is noise; one person making an abuse report is all it takes to get that ISP banned from the affiliate program.

Re: I fought my ISP's bad behavior and won

#3

Post by helfire » Tue, Dec 31, 2013, 10:03 PM UTC

JoshTriplett wrote: post #2

Very nicely done: reporting this as abuse to the companies offering these affiliate programs seems quite appropriate, and it sounds like they reacted appropriately. One person complaining to an ISP is noise; one person making an abuse report is all it takes to get that ISP banned from the affiliate program.

Thanks! I was in a state of hopelessness for a week or so till I had that idea.

Re: I fought my ISP's bad behavior and won

#4

Post by tdumitrescu » Tue, Dec 31, 2013, 10:04 PM UTC

"I will continue to monitor periodically their DNS entries and compare them with other public DNS servers."

This would make for a great watchdog site to provide visibility across different ISPs (and could also discourage other ISPs from pulling this crap).

Re: I fought my ISP's bad behavior and won

#5

Post by _RPM » Tue, Dec 31, 2013, 10:06 PM UTC

Gaming the system seems to be the secret to winning.

Re: I fought my ISP's bad behavior and won

#6

Post by helfire » Tue, Dec 31, 2013, 10:08 PM UTC

tdumitrescu wrote: post #4

"I will continue to monitor periodically their DNS entries and compare them with other public DNS servers." This would make for a great watchdog site to provide visibility across different ISPs (and could also discourage other ISPs from pulling this crap).

I think so too, though CDN's will mess with the results a bit. It would be nice if DNS had a way to sign/validate/somehow know the record you got was correct. Especially on the apex record as it can happen before ssl.

Re: I fought my ISP's bad behavior and won

#7

Post by Procrastes » Tue, Dec 31, 2013, 10:14 PM UTC

helfire wrote: post #6

tdumitrescu wrote: post #4

"I will continue to monitor periodically their DNS entries and compare them with other public DNS servers." This would make for a great watchdog site to provide visibility across different ISPs (and could also discourage other ISPs from pulling this crap).

I think so too, though CDN's will mess with the results a bit. It would be nice if DNS had a way to sign/validate/somehow know the record you got was correct. Especially on the apex record as it can happen before ssl.

It's interesting no one brought up DNSSEC[1]. Has anything happened there since 2010?

1. http://en.wikipedia.org/wiki/Domain_Name_System_Security_Ext...

Re: I fought my ISP's bad behavior and won

#8

Post by JoshTriplett » Tue, Dec 31, 2013, 10:15 PM UTC

helfire wrote: post #6

tdumitrescu wrote: post #4

"I will continue to monitor periodically their DNS entries and compare them with other public DNS servers." This would make for a great watchdog site to provide visibility across different ISPs (and could also discourage other ISPs from pulling this crap).

I think so too, though CDN's will mess with the results a bit. It would be nice if DNS had a way to sign/validate/somehow know the record you got was correct. Especially on the apex record as it can happen before ssl.

CDNs will indeed mess with the results, but it would still likely be possible to tell the difference between a legitimate result and a forged one, especially if you know something about the CDN structures used by major site. And the more people run it, the more likely you can detect anomalies, much like Perspectives does for SSL.

SSL, incidentally, seems like a major help here: you could detect common DNS hijackings by accessing the site via SSL. If you access https://amazon.com/ , an ISP hijacking the site would produce either a certificate error or a connection failure (depending on whether they even attempt to listen for SSL traffic).

Re: I fought my ISP's bad behavior and won

#9

Post by helfire » Tue, Dec 31, 2013, 10:16 PM UTC

Procrastes wrote: post #7

helfire wrote: post #6

Earlier quoted context omitted.

I think so too, though CDN's will mess with the results a bit. It would be nice if DNS had a way to sign/validate/somehow know the record you got was correct. Especially on the apex record as it can happen before ssl.

It's interesting no one brought up DNSSEC[1]. Has anything happened there since 2010? 1. http://en.wikipedia.org/wiki/Domain_Name_System_Security_Ext...

I was going to mention it, but I haven't found anyone using it or a usable implementation.

Re: I fought my ISP's bad behavior and won

#10

Post by philip1209 » Tue, Dec 31, 2013, 10:17 PM UTC

This is why you should encrypt your DNS.