Johannes Stezenbach wrote: > Yes, that's correct, I have strict-order set.
Ok. In that case I think a fully understand the problem. > > I use the resolvconf package to manage /etc/resolv.conf > (no server= in dnsmasq.conf). I also sometimes have to > use a VPN (using vpnc), thus I need strict-order for > correct lookups. But the bug is reproducable without the VPN. Yep, just using --strict order is enough. > > My main connection is usually a DSL line, and I get > two nameservers from pppoe. > > As a workaround, you might consider not using --strict-order, and specifying your VPN nameservers in /etc/dnsmasq.conf like so: server=/<domain of VPN>/<IP of nameserver> That way lookups which need to go to the VPN nameservers are send there, and everything else goes to the servers in /etc/resolv.conf There are a few unrelated issues to fix, so I anticipate a release to fix this in a week or so. The problem has existed in all dnsmasq releases for the last year or so. Cheers, Simon. > Thanks, > Johannes > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
