What I meant is that DNS resolution always fails at first, and then
after lots of tries, it starts to work. But now that I look at the logs,
it may just have been a fluke: it eventually works because one of the
reachable nameservers happens to reply fast enough.
--
You received this bug
No, that's the contrary, they reply too fast, in a sense. If you look at
the log I posted, dnsmasq does receive some kind of reply from the
unreachable nameservers. I don't know whether this is a crafted reply by
the firewall or whether the query actually reached the nameserver but it
replied with
Here is what I get when routing to the DNS servers goes through the
wrong interfaces. See bug #979067 for additional details on my setup.
Jun 25 12:50:51 dnsmasq[3799]: reading /var/run/dnsmasq/resolv.conf
Jun 25 12:50:51 dnsmasq[3799]: using nameserver yy.yy.36.37#53
Jun 25 12:50:51
See below for the results of various commands. Prefix xx.xx is the
Ethernet network while yy.yy is the wireless network. Both of them are
in the public IP range (in case it matters). I also added the result of
the dig command, without and with specifying a DNS server. Notice that
directly querying
Public bug reported:
My computer happens to be connected to two networks through eth0 and
wlan0. NetworkManager connects to both of them automatically and use
DHCP for both of them. Both networks are protected from the outside by
firewalls and they are lots of DNS servers (obtained
5 matches
Mail list logo
