lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

69
active users

#AdGuard

1 post1 participant0 posts today

I was talking to my kids last night a bit about why I put #AdGuard on the network. They were complaining about having to go off wifi to watch ads in their games.

Me: But the trackers!
Them: wat

Does anyone have a good video aimed at young people about why you should care about online #privacy?

Pihole on Freebsd? noGo and it is limited compared to Blocky
So a bit of searching did the trick:

I setup Blocky Grafana Prometheus node-exporter and more on a Freebsd jail to block ads / get insight into my network (and peers).

I used these guides and they helped me a lot: thanks to the authors!

Monitoring setup:
mostly-bsd.github.io/post/moni
Blocky
riesinger.dev/posts/ha-dns-adb
Dashboard for Blocky (and postgres):
grafana.com/grafana/dashboards

dummy screenshots ;)

Continued thread

Mais :nko_angry: comment ça peut fonctionne un coup et l'autre pas ...

Sur le OnePlus 6T (Android 11) :

Quand je passe par Rethink DNS (avec mon DNS) j'ai aucun accès a mes mails (Proton, Infomaniak, Free), Matrix mais pas de soucis pour me connecter a Iceshrimp ou Conversatin

Quand je passe le DNS direct dans la config Wi-Fi, j'ai les mail, Matrix, mais impossible de me connecter a mon instance Iceshrimp (Web ou app), Fdroid arrive pas joindre les serveurs.

Y a que Conversation qui fonction dans les deux cas en fait ...

#DNS #Adguard #RethinkDNS

uBlock Origin is a content blocker that supports the AdGuard URL Tracking filter, it may not be enabled by default.

The URL Tracking filter enhances privacy by removing tracking parameters from a URL.

Enable: Dashboard > Filter Lists > Privacy > AdGuard URL Tracking Protection (select checkbox) > Apply Changes

AdGuard post: adguard.com/en/blog/adguard-ur
URL: en.wikipedia.org/wiki/URL

Website: github.com/gorhill/uBlock

It's always DNS, right? If someone experiencing some strange issues with ubuntu, maybe this toot is for you.

tl;dr: switch from systemd-resolved to resolvconf.

I thought, the saying from the beginning was just something from the "old days". No DNS Problems in 2024 anymore, right? But Ubuntu taught me different.

Ubuntu is using systemd-resolved since 20.04 (if I'm correct). But I was shocked, when I was looking at my uptime kuma Container on a Ubuntu 22.04 LTS Host. It was constantly failing. Sometimes 3 services at the same time, sometimes just 1 service a day. One Check suddenly failed. 60 seconds later, the next check, switched back to green again. But all fails had the same error message: "getaddrinfo ENOTFOUND domain.com". Doesn't matter if they were internal domains or external. Sometimes some of them just failed.

I thought it could be an old Firewall Applience that were running at like 120% system utilization and were serving DHCP and (with this) internal DNS. But no. Not even high latencies from that Firewall. Then I thought it might be AdGuard (in a Docker Container). So I switched to PiHole. But the problems were still the same.

Then I turned on debug logs of systemd-resolved and found out that sometimes it was switching to the secondary DNS Server for whatever reason and just attaching the search domain to the following requests:

1. AAAA of demodomain.com
--> no answer (because only A were available)
2. A of demodomain.com
--> somehow failed, systemd-resolved switched to second DNS (debug log of systemd-resolved is hard to read, not sure why it somehow failed)
3. AAAA of demodomain.com.local
--> it just attached the searchdomain of the system to the domain which now resulting in errors from all following DNS Server

After another round of wrong requests it suddenly get back his head. But in the meantime, uptime kuma already failed.

The solution in my case: switch "back" to resolvconf package on Ubuntu. Which comes to at least one downside: it seems to not have an interface to netplan and/or networkmanager (which leads to manual creating and managing of resolv.conf, not via DHCP, bummer). But after I switched: Everything is working fine and without any problems since days.

"We" also have an open bug report since 3 years: github.com/systemd/systemd/iss

It's not exactly the same issue, but I think the root cause is connected somehow: it seems to be a problem of IPv6.
But a) I need (or better: want) IPv6 in my case/that network and b) WTF? How can this be a good solution to turn off IPv6 (github.com/systemd/systemd/iss)? Not to mention that we still need a solution for Post-IPv4.

By the way: If you still experiencing DNS issues inside Docker Container, maybe Alpine could be another issue: martinheinz.dev/blog/92

GitHubsystemd-resolved sometimes stops resolving · Issue #21123 · systemd/systemdBy gudvinr