> This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent any further occurrences.
Do note this is not a solution for those using non-Azure resolvers
provided via DHCP through their
Microsoft has created an incident for this.
https://azure.status.microsoft/en-us/status reports:
Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors
- Investigating
Starting at approximately 06:00 UTC on 30 Aug 2022, a number of
customers running Ubuntu 18.04 (bionic) VMs rece
We've just had the same problem, on multiple VMs running in Azure.
In the dpkg log we can see that systemd was indeed updated (times in
UTC):
2022-08-30 06:31:18 status unpacked udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:18 status half-configured udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:19
This problem stems from the inclusion of the fix for CVE-2015-5180. The
internal number for A + changed in glibc (from T_UNSPEC=62321 to
T_QUERY_A_AND_=439963904).
In TCPDump, we see queries going out for TYPE62321 (the former internal
number for A+).
I think busybox uses the old sym
4 matches
Mail list logo
