Thanks for the responses, both. Not sure how I didn't find that thread [1] when I searched this category before posting - I think I just searched for DNS in the title, doh! Anyway, it matches what I see, and the workaround, for me, of simply purging systemd-resolved, makes the issue go away.
This package certainly seems to be installed and enabled by default in the official Debian AWS EC2 AMIs, but doesn't seem to be essential.
The symptoms of the issue seem to be limited to resolving CNAMEs, or at least I only see it with CNAMEs and not A records. Also, disabling IPv6 (I tested using nc and then nc -4) stops the issue happening.
[1] viewtopic.php?t=157142
Code:
apt purge --auto-remove systemd-resolvedThe symptoms of the issue seem to be limited to resolving CNAMEs, or at least I only see it with CNAMEs and not A records. Also, disabling IPv6 (I tested using nc and then nc -4) stops the issue happening.
[1] viewtopic.php?t=157142
Statistics: Posted by andyholtmacc — 2024-04-09 09:12