Post BAXZ9XojKKjt084r2G by niconiconi@mk.absturztau.be
 (DIR) More posts by niconiconi@mk.absturztau.be
 (DIR) Post #BAXW35CCWo8MdKHbP6 by letoams@defcon.social
       0 likes, 0 repeats
       
       @niconiconi seems a systemd-resolved issue ?
       
 (DIR) Post #BAXW35RRc8KLObPmAC by niconiconi@mk.absturztau.be
       0 likes, 0 repeats
       
       @letoams@defcon.social systemd-resolved is NOT installed.
       
 (DIR) Post #BAXZ9XZ8GKGKDkmOiu by letoams@defcon.social
       0 likes, 0 repeats
       
       @niconiconi oh gods, systemd-networkd independently mucks with DNS too. Sigh
       
 (DIR) Post #BAXZ9XojKKjt084r2G by niconiconi@mk.absturztau.be
       0 likes, 1 repeats
       
       @letoams@defcon.social Stop blaming systemd for all the world's real and imagined problems in existence. This problem is clearly just a default fallback behavior of glibc, not systemd. It's reproducible with a fresh Live ISO of Devuan Excalibur 6.1.1 amd64 minimal in QEMU, it's a Debian fork with SysV init, there are NO systemd processes running at all. You boot with kernel cmdline hostname=example.club, set the hostname in the system via hostname example.club, and overwrite /etc/resolv.conf with nameserver 8.8.8.8. The problem is 100% reproducible. In fact, using systemd may have saved me in this case, because systemd has an empty UseDomain by default for security, but I bypassed it, and glibc doesn't do this hardening by default.
       
 (DIR) Post #BAXkbi8HfQEgb7rBPU by letoams@defcon.social
       0 likes, 0 repeats
       
       @niconiconi can you show your nsswitch.conf ?
       
 (DIR) Post #BAXkbiOagnHPPhUCpM by niconiconi@mk.absturztau.be
       0 likes, 0 repeats
       
       @letoams@defcon.social Untouched default.