• sunzu@kbin.run
    link
    fedilink
    arrow-up
    22
    ·
    5 months ago

    Aint all of peasant level ISPs bootstrapping unencrypted DNS requests?

    Get you a fucking VPN and a good router, flash openwrt and put vpn on the router. Deny these parasites the data.

    or at leas get a good VPN for your main PC and cellphone. they monitor your traffic, they sell it. you know this, act on it.

      • Bookmeat@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 months ago

        With DoH, the first request to find the https DNS resolver itself is unencrypted rendering it subject to hijacking.

        Correct me if I’m wrong, but that’s how I understand it.

        • Spotlight7573@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          5 months ago

          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
            link
            fedilink
            English
            arrow-up
            3
            ·
            5 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.

        • plz1@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          5 months ago

          You’re not wrong, but you can bootstrap that request, too. It makes it more complicated, but I know NextDNS has taken steps to prevent that type of hijack with their mobile apps.

        • SteveTech@programming.dev
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          The HTTPS certs are designed to prevent MITMing, but if it’s still a worry or the domain is blocked by DNS, you can manually find the IP and add it to your hosts file instead.