@evan Perhaps I should have prefaced with "apart from convince, there's another big reason folks don't do email themselves" or am I misunderstanding the point of your post?
Notices by Pieter Lexis (lieter@mastodon.lieter.nl)
-
Embed this notice
Pieter Lexis (lieter@mastodon.lieter.nl)'s status on Friday, 29-Nov-2024 06:04:38 JST Pieter Lexis
-
Embed this notice
Pieter Lexis (lieter@mastodon.lieter.nl)'s status on Friday, 29-Nov-2024 02:05:09 JST Pieter Lexis
@evan The biggest issue with self-hosting (or running email) is the fact that the big free email providers tend to reject your mails. Even when you're adhering to all the standards they require. @mwl wrote a book about it. It is unfortunate that email is no longer a properly federated service...
-
Embed this notice
Pieter Lexis (lieter@mastodon.lieter.nl)'s status on Friday, 17-Nov-2023 00:56:23 JST Pieter Lexis
@aral DNSVIZ reports no issues: https://dnsviz.net/d/kittens.small-web.org/ZVY34g/dnssec/
You could try to send SIGUSR1 to resolved when the failure occurs, that makes resolved dump info on its upstreams.
You could also enable tracing in systemd-resolved to see if the problem is systemd-resolved or further upstream. Tracing can be enabled by creating a service override and restarting systemd-resolved.
```
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
```