January 11, 2017 10:07 am
There's a tip in the tips queue about Internode's approach to site blocking I'd like to explore.
As of a few days before Christmas, the tipster reported to s115a.com "Internode has activated its block".
The ISP's splash/notification page looks like this:
But interestingly, tipster writes "as far as I can tell, a DNS change does not bypass it."
We know that people quickly worked a way around the blocks, but could this imply that some ISPs have a slightly stronger approach to blocking than others?
I don't want to get into publishing ways to get around the blocks, but I'm interested if any readers have worked out how to get around Internode's (and more widely, TPG's) approach.
UPDATE 12 Jan 2017
According to our tipsters it seems that getting around TPG's block is as "easy" as 188.8.131.52 - that is, setting the computer to use Google's public DNS service rather than using the ISPs default.