Alex Samorukov

Is it possible to backport patch to systemd 238 in stable?

Was able to reproduce issue also with cache disabled. At the moment o see 2% requests failing (based on the checks status): ``` check=sysdig-network output="OK - collector.sysdigcloud.com is reachable. |...

Was able to reproduce it w/o consul.

Ok, so few more notes: 1. I was able to trigger this bug with curl, w/o consul. 2. Not able to reproduce using dig on 127.0.0.53, so it is likely...

@pothos very very possible. But not sure which exactly. Now going to reproduce it on clean non modified instance running in default vpc. 2% of the DNS failures is a...

@pothos do you have an idea how to turn off systemd-resolved completely? I tried to mask it but looks like it is required to create /etc/resolv.conf file in that case...

@pothos thank you, will try that! BTW, i was able to reproduce the bug on a very clean setup, from your AMI, with a 0 customization. Steps performed: 1. Run...

@pothos i was not able to identify exact pattern, but from the logs its looking that it happens when cache is getting expired, what makes me thinking about some race....

@pothos one thing to note - i was not able to trigger that with `watch -n 0.1 resolvectl query collector.sysdigcloud.com`. It makes me thinking that only gethostbyname() calls are impacted.

@pothos your workaround seems to work, thank you. Will use it for now and wait for upstream fix. Let me know if any tests needed.