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

[Martin]

Dear All,

Wheeeee! Time flies!!!


>> On 14 August 2020 13:20:58 BST, Phil Bass via Nottingham wrote:
>>     It was good to meet a few of you on jitsi last night.

Phil, good to see you and very welcome to the group.

Hope you can join us again tonight!


Good comments all round. Good to see you online Fay.


My experience of sytemd-dhcp on a Raspbian (Rasberyy Pi) system has been
that:

An IP address is correctly picked up from the dhcp server;

A gateway address provided by the dhcp server is ignored;

A DNS server address provided by the dhcp server is likewise ignored;

Regardless, the sytemd-dhcp setup blindly insists on setting a x.x.x.1
gateway address;

And the DNS always sets to use the Google DNS servers...


Aside: I have a gateway addres that is not on x.x.x.1 and I run my own
DNS...


In what I see as the "systemd" way of doing things, rather than waste
time reading manuals/documentation and the web, and to follow with the
systemd ethos of deliberately breaking all compatibility and instead go
for an immediate quick short-term 'fix' workaround:

I simply have a script that copies a hand-crafted resolv.conf to blindly
overwrite the /etc/resolv.conf. Works every time!

Easy?! :-)



More seriously for my example:

There is a fantastic mystery as to how systemd might come by the
contorted confabulations thus conjured or contrived:

Whatever, at least for my one example on Raspbian, systemd (arrogantly,
shoddily,) doesn't follow the long established protocols...

All very fragile...

All along the way of a myopic arrogant shoddy mess?


:-)

To discuss?!

Cheers,
Martin




On 15/08/2020 11:09, Phil Bass via Nottingham wrote:
> Thanks, Fay.
> 
> I tried masking systemd-resolvd and rebooted but that didn’t help. Then
> I looked at my /etc/resolv.conf. It was a symbolic link to
> ../run/systemd/resolve/stub-resolv.conf, which did not exist. In fact,
> there was no /run/systemd/resolve/ directory at all. I guess that
> explains it (sort of).
> 
> So, I created a minimal /etc/resolv.conf file and Internet access now works.
> 
> I’m guessing that Linux Mint 20 is broken but very few users notice
> because almost all of them have upgraded from a working earlier version.
> Can anyone here confirm that theory?
> 
> Phil Bass
> phil.bass at icloud.com <mailto:phil.bass at icloud.com>
> 
> 
>> On 14 Aug 2020, at 13:51, Fay Knight via Nottingham
>> <nottingham at mailman.lug.org.uk <mailto:nottingham at mailman.lug.org.uk>>
>> wrote:
>>
>> 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 <mailto: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 <mailto:phil.bass at icloud.com>
>>
>>
>>
>> -- Sent from /e/ Mail.-- 
>> Nottingham mailing list
>> Nottingham at mailman.lug.org.uk <mailto:Nottingham at mailman.lug.org.uk>
>> https://mailman.lug.org.uk/mailman/listinfo/nottingham
> 
>