Oriel — AI & technology worth noticing, every day.

So my ISP was hijacking my DNS

Web page · https://karthihegde.dev/posts/dns_tampering

First seen by Oriel on .

AI summary

This article explains how an ISP hijacked DNS responses and clarifies what Unbound, DNSSEC, DoH, DoT, VPNs, and encrypted upstream resolvers do and do not protect against.

  • The author found most DNS providers returned an ISP-owned IP, while Cloudflare's DoH endpoint returned the correct address.
  • Self-hosted Unbound does not prevent tampering unless it forwards queries through an encrypted connection such as DoT.
  • DNSSEC authenticates responses rather than encrypting queries, and invalid tampered responses produce SERVFAIL when validation applies.
  • DoH and DoT protect traffic in transit but require trusting the resolver, which can still alter responses.
  • The setup uses AdGuard with dnscrypt-proxy, plus Cloudflare as a fallback for containers where DNS availability is critical.

#dns #dnssec #doh and dot #homelab

Generated by gpt-5.6-sol. Check the original for details.

Metric trends

Last 30 days · Up to 120 recorded samples per source and metric, with reposts kept separate · First and latest retained

Points

Score reported by the source.

  • Hacker News: 231, latest observation ; +227 over observed period since
  • Lobsters: 109, latest observation ; +108 over observed period since

Comments

Comment count reported by the source.

  • Hacker News: 202, latest observation ; +201 over observed period since
  • Lobsters: 19, latest observation ; +19 over observed period since

Aliases

SourceExternal IDURL
Hacker News50364860https://www.karthihegde.dev/posts/dns_tampering Read discussion
Lobsterscozhtghttps://karthihegde.dev/posts/dns_tampering Read discussion