I confirmed this in a Focal container:
root@focal:~# resolvectl query client.wvd.microsoft.com client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-yq1-4474575f.sip.p.azurewebsites.windows.net'
This limit has in fact been increased to 16 upstream, which is the case for Jammy and newer (https://github.com/systemd/systemd/blob/34c4496ef2711d2a924e6f88fe3ff31cda080115/src/resolve/resolved-dns-query.c#LL17C12-L17C12).
I don't think this will be prioritized, but I don't see why it can't be fixed in a future SRU.
I confirmed this in a Focal container:
root@focal:~# resolvectl query client. wvd.microsoft. com wvd.microsoft. com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod- yq1-4474575f. sip.p.azurewebs ites.windows. net'
client.
This limit has in fact been increased to 16 upstream, which is the case for Jammy and newer (https:/ /github. com/systemd/ systemd/ blob/34c4496ef2 711d2a924e6f88f e3ff31cda080115 /src/resolve/ resolved- dns-query. c#LL17C12- L17C12).
I don't think this will be prioritized, but I don't see why it can't be fixed in a future SRU.