this post was submitted on 07 Aug 2024
59 points (95.4% liked)

Technology

59605 readers
3345 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
59
ISPs Hijack Cloudflare/Google DNS Requests, Ending Site-Blocking Workarounds. (torrentfreak.com)
submitted 3 months ago by ModerateImprovement@sh.itjust.works to c/technology@lemmy.world
17 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Spotlight7573@lemmy.world 6 points 3 months ago (1 children)

Don't most DoH resolversl settings have you enter the IP (for the actual lookup connection) along with the hostname of the DoH server (for cert validation for HTTPS)? Wouldn't this avoid the first lookup problem because there would be a certificate mismatch if they tried to intercept it?

[โ€“] Bookmeat@lemmy.world 3 points 3 months ago

Well, that's the thing. I've seen many instances where the DoH field is required to be a FQDN, not an IP. This always struck me as strange, but I didn't think much on it until recently.