this post was submitted on 19 Sep 2023
611 points (95.0% liked)
Asklemmy
43791 readers
1613 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.