Hmm, not exactly #1003842, since you don't have the problem that some
nameservers are "screening off" others with NXDOMAIN.
The worst we can say about dnsmasq in this context is that it could
behave better in the case where several listed upstream nameservers are
unreachable.
** Also affects: dns
The first problem is with your routing. Address yy.yy.34.35 is
presumably to be reached via yy.yy.72.0/24 but the kernel does not know
this.
Second problem is bug #1003842 again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
** Summary changed:
- Please reenable dnsmasq --strict-order
+ DNS unresponsive/slow when different DNS are provided by wifi and wired
connected to different networks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ub
3 matches
Mail list logo