abusive_isps

This is an old revision of the document!


Abusive ISPs

These are Internet Service Providers that have been found to tamper with your DNS (or OpenNIC related) traffic, do note that this list is only for previously mentioned abuse, nothing else.

Some abusive ISPs will intercept DNS traffic on port 53 and return results from their own servers instead. This makes access to alternative TLDs difficult, and is a privacy concern as it allows the ISPs to carry out more detailed logging of the domains you resolve.

Some OpenNIC DNS servers also listen on an alternative port (generally 5353) which is less likely to be tampered with by ISPs.

To test if an ISP is tampering with DNS traffic, you can use the dig command from the dnsutils package. Select a server from the Tier 2 page which supports an alternative port. In my example I have used 106.186.17.181. First, try querying for the root zone (.) on the default port:

dig SOA . @106.186.17.181
...
.	58346	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2015080300 1800 900 604800 86400

You can see from the returned SOA above that the DNS request has been hijacked by the ISP as a.root-servers.net is not an OpenNIC DNS server. If the SOA you get looks more like the one below, then your ISP is probably not hijacking your DNS requests.

Now try again on the alternative port:

dig SOA . @106.186.17.181 -p 5353
...
.	86319	IN	SOA	ns0.opennic.glue. hostmaster.opennic.glue. 2015080301 1800 900 604800 3600

You can see that the SOA returned is OpenNIC's, meaning no hijacking has taken place on the alternative port. If this result differs from the previous result or the first result times out with connection timed out; no servers could be reached, then your ISP is likely to be hijacking DNS.

Please refer to the answer of this question to use iptables to reroute your DNS traffic to an alternative port on an OpenNIC server. Remember to change the server's IP address.

You could also contact your ISP to complain about their use of DNS hijacking.

This list is very incomplete. If you are certain that your ISP is hijacking DNS or is involved in other questionable practices, please add it below.

Country ISP Reported Reporter 53/udp interception Level Notes
- Vultr/Choopa 2017 fusl yes blocking of selective domains DPI on UDP/53, blocks any DNS request containing the text minexmr.com. in the query name (proof)
United States AT&T 2017 news no NXDOMAIN search engine redir http://www.att.net/dnserrorassist/about/ (screenshot), https://forums.att.com/t5/AT-T-Internet-Features/ATT-DNS-Assist-Page/td-p/5108480 (screenshot)
United States CenturyLink 2017 some user on #opennic no NXDOMAIN search engine redir Reproduced by fusl - NXDOOMAIN redirect to 198.105.244.23 and 198.105.245.23 which redirects to http://webhelper.centurylink.com/index.php?origURL=xxx&r=&bc=
Peru Bitel 2017 Tedel on #opennic unknown FIXME unknown FIXME IRC conversation log
United States Comcast 2009 news no NXDOMAIN search engine redir http://www.theregister.co.uk/2009/07/28/comcast_dns_hijacker/, disabled in August 2009
Canada Rogers 2007 news no HTML ad content injection http://www.dslreports.com/shownews/Rogers-Uses-Deep-Packet-Inspection-for-DNS-Redirection-96239
  • /wiki/data/attic/abusive_isps.1509678496.txt.gz
  • Last modified: 6 years ago
  • by fusl