Package: dnsmasq-base Version: 2.87-1 Followup-For: Bug #1020830 Maybe the relation to no-negcache was just a coinsidence. I now experienced again not respecting the server entry, which the minimal config I provided before, which was working.
I currently see that eg right after a NetworkManager restart sub1.domain1.net is sent to the dns defined iva server=/domain1.net/1.2.3.4, and 15 minutes later sub2.domain1.net is not sent to that one. Will try to get more information and try to see if I can find another relation/influence to the behavior. Best regards Michael -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (504, 'unstable'), (503, 'testing'), (502, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-2-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dnsmasq-base depends on: ii adduser 3.129 ii libc6 2.35-1 ii libdbus-1-3 1.14.2-1 ii libgmp10 2:6.2.1+dfsg1-1 ii libhogweed6 3.8.1-2 ii libidn2-0 2.3.3-1+b1 ii libnetfilter-conntrack3 1.0.9-2 ii libnettle8 3.8.1-2 ii libnftables1 1.0.5-1 Versions of packages dnsmasq-base recommends: ii dns-root-data 2021011101 dnsmasq-base suggests no packages. -- no debconf information
