[Nottingham] systemd-resolved Failed to send hostname reply: Invalid argument

[Fay Knight]

Hi Phil,

From my limited knowledge of systemd-resolved I don't believe it's strictly necessary, so yes disabling it is worth a try.  You might need to also check the contents of the /etc/resolved.conf file to check that it's pointing to a known-good DNS server.  Or alternatively you could simply restart the machine afterwards and see if it's now reaching the internet.  

Fay 



On 14 August 2020 13:20:58 BST, Phil Bass via Nottingham <nottingham at mailman.lug.org.uk> wrote:
>Hi, guys.
>
>It was good to meet a few of you on jitsi last night.
>
>A few days ago I installed Linux Mint 20 on an old Windows laptop. I
>haven’t fiddled with any settings (my sysadmin credentials are somewhat
>lacking but I can follow instructions 🙂). The machine connects to my
>WiFi but can’t access the Internet. The Logs app contains multiple
>error messages that say:
>
>systemd-resolved Failed to send hostname reply: Invalid argument
>
>Googling for this error message throws up a GitHub thread
><https://github.com/systemd/systemd/issues/11626> dating from Feb 2019.
>The problem was originally associated with sleep/wakeup in Arch Linux
>but has also been reported as a permanent problem preventing access to
>the Internet and in Ubuntu. There’s no resolution in that thread and
>the last post was yesterday.
>
>I’ve also found a thread on a Manjaro forum
><https://forum.manjaro.org/t/i-broke-my-dns-configuration-limited-connection-to-internet-on-manjaro/122487/28>
>that suggests masking or disabling systemd-resolved and that has solved
>the problem for the original poster. Is that worth a try?
>
>Phil Bass
>phil.bass at icloud.com

-- Sent from /e/ Mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/nottingham/attachments/20200814/191a1e76/attachment.html>