Bug#969903: This is can be closed

Nicolas Évrard nicolas.evrard at b2ck.com
Tue Sep 8 17:23:59 BST 2020

Previous message (by thread): Bug#969903: /usr/bin/resolvectl: systemd-resolved resolves name differently than dig
Next message (by thread): Bug#969903: marked as done (/usr/bin/resolvectl: systemd-resolved resolves name differently than dig)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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: nicolas.evrard at b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Previous message (by thread): Bug#969903: /usr/bin/resolvectl: systemd-resolved resolves name differently than dig
Next message (by thread): Bug#969903: marked as done (/usr/bin/resolvectl: systemd-resolved resolves name differently than dig)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Pkg-systemd-maintainers mailing list