Comment 2 for bug 1921636

Revision history for this message
Dan Streetman (ddstreet) wrote :

Quite a number of CNAME redirects you have there!

The resolved logs appear to be fine, e.g.:
Mar 28 11:30:27 castle systemd-resolved[73519]: Added positive unauthenticated cache entry for standard.t-0009.t-msedge.net IN A 30s on enp4s0f0/INET/10.18.1.1
Mar 28 11:30:27 castle systemd-resolved[73519]: Added positive unauthenticated cache entry for standard.t-0009.t-msedge.net IN A 30s on enp4s0f0/INET/10.18.1.1

And when I try to resolve your example hostname it only goes through 2 CNAMES:
$ host static-exp1.licdn.com
static-exp1.licdn.com is an alias for 2-01-2c3e-003d.cdx.cedexis.net.
2-01-2c3e-003d.cdx.cedexis.net is an alias for cs1404.wpc.epsiloncdn.net.
cs1404.wpc.epsiloncdn.net has address 152.199.24.163
cs1404.wpc.epsiloncdn.net has IPv6 address 2606:2800:21f:fedd:8b7a:88ab:fc7e:fa3b

Do you have a different example hostname that I can try to reproduce this with?