• pacjo@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I don’t know. If I use chrome on the same device there are no issues. You can’t be certain but I think it’s not DNS.

      • ddh@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        That might be evidence in favour of it being a DNS issue. Google Chrome doesn’t always use the system’s DNS.

        • pacjo@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Good to know, but for now it seems like the issue solved itself. Will report later if anything changes.

    • Bizarroland@kbin.social
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      It’s almost never DNS, except when it is.

      Try setting your DNS to adguards default servers and see if that helps.

      Those addresses are 94.140.14.14 and 94.140.15.15.

      If you don’t want to do that you could always set it to 1.1.1.1 but adguards DNS servers also help filter ads so that’s nice.