RC RANDOM CHAOS

When Your ISP Hijacks DNS: Real Technical Solutions

· via Hacker News

Original source

So my ISP was hijacking my DNS

Hacker News →

An engineer discovered their ISP was hijacking DNS queries and returning tampered IP addresses. Different DNS providers returned the same address, but Cloudflare’s DoH endpoint returned different results, revealing the first address belonged to their ISP.

Traditional DNS resolution occurs over unencrypted UDP across multiple nameserver queries, allowing ISPs to snoop and tamper. While self-hosting Unbound (a local DNS resolver similar to Cloudflare’s 1.1.1.1) doesn’t inherently prevent this, configuring it to forward queries over DoT (DNS over TLS) encrypts the connection to an upstream resolver. DNSSEC, often misunderstood as a security solution, uses cryptographic signatures to verify authenticity rather than encrypting traffic. According to an October 2026 Defaults.Exposed census, only 7.03% of graded domains have valid, fully validating DNSSEC chains. DoT and DoH encrypt the connection to prevent ISP tampering but require trusting the resolver operator. ISPs can still observe visited sites through SNI inspection during TLS handshakes or by analyzing destination IP addresses.

The author uses AdGuard with dnscrypt-proxy handling upstream DNS queries over DNSCrypt for in-transit encryption. Cloudflare is configured as a fallback for containers that cannot tolerate DNS failures, though AdGuard remains the primary resolver. This approach avoids creating a single point of failure if the self-hosted DNS server becomes unavailable.

Read the full article

Continue reading at Hacker News →

This is an AI-generated summary. Read the original for the full story.