Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

5.4K
active users

techhub.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#resolved

1 post1 participant0 posts today
Public
chris@strafpla.net

Because the excellent (and beloved for a decade or so) #reeder by @rizzi does not support #TLSClientAuth for feeds* I spent a few hours on Yak-Shaving and on learning about #caddyserver #systemd-#resolved and - in the end - about #iCloudPrivateRelay.
If a local request is handled like an external request it may be because ... it's coming in as an external request.
___
* I’m sure I’m the only one left on the planet who has rss feeds with Client Certificates, so this is fine!

Public *
MetaFilter

Ask Me synchronicity ... 18 years later

In 2006, ninazer0 asked for help identifying three works of English juvenile historical fiction, later finding the answer to one of the mystery texts.

In 2024, tangerine asked about mid-century kids' historical fiction about the Hanseatic League, and paduasoy's suggestion was not the author OP was looking for -- but it did resolve the remaining earlier mystery! Then melisande added more info for the earlier question. Delightful!

ask.metafilter.com/378170/Book

Art by Eddi van W. on Flickr: black and white close-up image of an old-fashioned clock face with roman numerals and ornate hands with translucent drifting wave forms wafting in front of it
#resolved#AskMetafilter#question
Public
Marcos Dione

#til

* It's really hard to find solutions for `resolved` issues because many forums add "[RESOLVED]" to the title of threads with a working solution.
* Many of the features listed in yesterday's link (see en.osm.town/@mdione/1117707555) only work in 'modern' `resolved`s. Check whether you're not running an old version.
* if you get `SERVFAIL` from #resolved, check the system's logs. I was getting `Got packet on unexpected IP range, refusing`. There was a stray #iptables rule.

OSM Town | Mapstodon for OpenStreetMapMarcos Dione (@mdione@en.osm.town)#til: * only the first 3 servers in `/etc/resolv.conf` are used by #glibc's resolver, the rest are ignored * there's an option in #NetworkManager's config to force all traffic to go through a VPN or not * depending on your NSS and `resolved` config, you might never reach the #DNS servers listed in `/etc/resolv.conf` * even if your default IP route doesn't go through a #VPN, DNS queries might More info at https://blogs.gnome.org/mcatanzaro/2020/12/17/understanding-systemd-resolved-split-dns-and-vpn-configuration/ #ItsAlwaysDNS
#ItsAlwaysDNS
Replied to Petr Menšík :fedora:
Public
Marcos Dione

@pemensik which is at the same time good and bad. If I was trying to debug a #DNS issue in one app that uses #glibc's 3-servers resolver with a tool that uses them all, it might as well work for the tool and not the app. I guess one has to be aware of that, hence my post.

That's probably why it makes sense to use #resolved with the stub handling of `/etc/resolv.conf`; that and the fact that can do much better resolving, if configured correctly.

#ItsAlwaysDNS
Public
farcaller

I can't stand this anymore. dig @127.0.0.53 works, but curl can't resolve anything. Fuck you #resolved, fuck you in particular for making the DNS issues completely opaque.

services.resolved.enable = false. I can totally manage my /etc/resolv.conf by hand becasue I resolve everything through coredns rules either way.

#DNS shouldn't be this complicated! The only job resolved does is resolving shit, and I don't want to know why it can resolve it via UDP fine, but not via whatever curl talks to it

ExploreLive feeds
About