[sf-lug] Mail problems (or Firefox, or systemd,...)

Justin Noor justinnoor.io at gmail.com
Sun Dec 16 07:52:58 PST 2018


Systemd-resolvd has a peculiar existence. It doesn’t seem to solve any
problems or improve any pre-existing tools. It claims to be a fully
featured DNS resolver but could not possibly compete with Unbound. It
appears to be an unnecessary abstraction that confuses the sh*t out of
things.

On Sat, Dec 15, 2018 at 10:07 PM Rick Moen <rick at linuxmafia.com> wrote:

> Quoting Ken Shaffer (kenshaffer80 at gmail.com):
>
> > Looks like I missed the forum discussion of the comcast/systemd-resolve
> > problem:
> > https://ubuntuforums.org/showthread.php?t=2406399
>
> Short version (https://moss.sh/name-resolution-issue-systemd-resolved/):
> One of the innumerble ways systemd-resolved sucks rocks is in failing to
> follow DNS standards, such as DNSSEC's RRSIG digital signatures.
>
> (From above link:)
>
> # host -t RRSIG keyserver.ubuntu.com 127.0.0.53
> Using domain server:
> Name: 127.0.0.53
> Address: 127.0.0.53#53
> Aliases:
> Host keyserver.ubuntu.com not found: 1(FORMERR)
> #
>
> You'd probably have seen entries about the DNS resolution error pointing
> the finger directly at systemd-resolved if it had occurred to you to
> look in /var/log/syslog -- but it didn't, right?  Nota bene:  When Unix
> processes have problems, they very often mutter about that into log files.
> Log files are your friend.  Get to know them.  Many mysterious goings-on
> will become much less so.
>
> And, Ken, are you going to be implementing daft solutions from
> nobody-in-particular on ubuntuforums.org?  Like hardwiring an IP address
> instead of 'pop3.comcast.net' to compensate for systemd-resolved's
> inability to correctly handle DNSSEC?  Or migrating everything from a
> POP3 account to an IMAP account?
>
> See, that's the problem with following advice off ubuntuforums.org.
> It's the blind leading the blind.
>
> How about considering -- oh, just spitballing, here -- disabling
> systemd-resolved, seeing that it's bugware 'n' all?  Like, addressing
> the source of the error, rather than just limping around it?
>
>
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/<br>
> Related Information <br>
> http://www.shallowsky.com/blog/<br>
> http://explainshell.com/ <br>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20181216/0cefd6e0/attachment.html>


More information about the sf-lug mailing list