Vitaly to Asklemmy@lemmy.mlEnglish • 1 year agoWhy do you use firefox?upload.wikimedia.orgimagemessage-square430fedilinkarrow-up1631arrow-down135 cross-posted to: technology@beehaw.orgfoss@beehaw.orglinux@lemmy.ml
arrow-up1596arrow-down1imageWhy do you use firefox?upload.wikimedia.orgVitaly to Asklemmy@lemmy.mlEnglish • 1 year agomessage-square430fedilink cross-posted to: technology@beehaw.orgfoss@beehaw.orglinux@lemmy.ml
minus-squareBizarrolandlinkfedilink3•1 year agoIt’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.
minus-squarepacjolinkfedilink2•1 year agoI 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.
minus-squareddhlinkfedilinkEnglish4•1 year agoThat might be evidence in favour of it being a DNS issue. Google Chrome doesn’t always use the system’s DNS.
minus-squarepacjolinkfedilink2•1 year agoGood to know, but for now it seems like the issue solved itself. Will report later if anything changes.
Could be DNS?
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.
Nah, it can’t possibly be DNS…
Narrator: It was DNS. It’s always DNS.
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.
That might be evidence in favour of it being a DNS issue. Google Chrome doesn’t always use the system’s DNS.
Good to know, but for now it seems like the issue solved itself. Will report later if anything changes.