Differences

This shows you the differences between two versions of the page.

--- abusive_isps [2019-06-09T21:21:56Z] – [Abusive ISP List] fusl
+++ abusive_isps [2026-11-06T05:45:42Z] (current) – fusl
@@ Line 23: / Line 23: @@
 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.
+Note that absence of evidence != evidence of absence, meaning that even if this test shows no tampering happening, it's still possible for your ISP to be tampering with DNS requests and responses in a transparent manner.
 ==== What can I do about it? ====
-Please refer to the answer of [[https://unix.stackexchange.com/questions/144482/|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.
+Multiple workarounds exist for different cases:
-You could also contact your ISP to complain about their use of DNS hijacking.
+  * Use DoH, DoT, or DNSCrypt where possible. Either of those will transmit your data fully encrypted without your ISP being able to see or tamper with your DNS traffic.
+  * [[https://unix.stackexchange.com/questions/144482/|Redirect outbound DNS traffic]] to an alternative port supported by the selected DNS resolver.
+  * Contact your ISP to complain about their use of DNS hijacking.
 ==== Abusive ISP List ====
@@ Line 40: / Line 44: @@
 | Peru           | Bitel          | 2017-06-23 |            | Tedel on #opennic          | ?   | ?                                | {{:abusive_isps:bitel.txt|IRC conversation log}} |
 | United States  | AT&T           | 2017-03-27 |            | //news//                   | no  | NXDOMAIN search engine redir     | [[https://web.archive.org/web/20190127173703/http://www.att.net/dnserrorassist/about/|ETM Details with Opt-Out Option]] ({{:abusive_isps:att1.png?linkonly|screenshot}}), [[https://web.archive.org/web/20190127173856/https://forums.att.com/t5/AT-T-Internet-Features/ATT-DNS-Assist-Page/td-p/5108480|ATT DNS Assist Page - AT&T; Community]] ({{:abusive_isps:att2.png?linkonly|screenshot}}) |
+| India          | ACT Fibernet   | 2016-09-17 | 2026-11-03 | //blog post//              | yes | ?                                | [[https://shantanugoel.com/2016/09/17/indian-isp-act-fibernet-blocks-bit-ly-does-dns-hijacking/|Indian ISP ACT Fibernet blocks bit.ly. Does DNS Hijacking :: Shantanu Vs The World]] [[https://www.karthihegde.dev/posts/dns_tampering|So my ISP was hijacking my DNS - Karthikey Hegde]] |
 | -              | Level3         | 2015-11-13 | 2019-06-09 | gorbilax on reddit         | no  | NXDOMAIN search engine redir     | [[https://web.archive.org/web/20190609210007/https://www.reddit.com/r/networking/comments/3sm36w/level3_42214222_dns_servers_redirecting_to_search/|Level3 4.2.2.1/4.2.2.2 DNS servers redirecting to search page : networking]], NXDOMAIN redirect to ''23.202.231.167'' and ''23.217.138.108'' on their well-known ''4.2.2.1''-''4.2.2.6'' servers, {{:abusive_isps:level3.txt|proof}} |
 | United States  | T-Mobile US    | 2015-07-20 |            | thefinn93 on reddit        | no  | NXDOMAIN search engine redir     | [[https://web.archive.org/web/20190127174032/https://www.reddit.com/r/tmobile/comments/3dyk1h/how_do_i_turn_of_nxdomain_hijacking/|How do I turn of NXDOMAIN hijacking?]] |