This issue can be closed because after investigating with tcpdump it seems that it's 192.168.1.1 that replies something different if the query comes from dig or from systemd-resolved (I don't know how he knows that). -- Nicolas Évrard - B2CK SPRL E-mail/Jabber: [email protected] Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
- Bug#969903: /usr/bin/resolvectl: systemd-resolv... Nicolas Évrard
- Bug#969903: This is can be closed Nicolas Évrard
- Bug#969903: marked as done (/usr/bin/resol... Debian Bug Tracking System
