<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>Hello,<br></div><div><br></div><div>Here's an info dump, which hopefully gives a bit more context:<br></div><div><br></div><div>Hosts file:<br></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">192.168.1.200 some.domain<br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">10.23.0.2 some.domain</span><br></div><div><br></div><div>Log entry:<br></div><div><br></div><pre id="output" style="width:100%;height:100%;max-height:650px;overflow-y:scroll;">Apr 6 17:03:58 dnsmasq[549]: query[A] some.domain from 192.168.1.92
Apr 6 17:03:58 dnsmasq[549]: /hosts.conf some.domain is 192.168.1.200
Apr 6 17:03:58 dnsmasq[549]: /hosts.conf some.domain is 10.23.0.2<br></pre><div><br></div><div>Local Shell:<br></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">$ dig some.domain @10.23.0.2 +short<br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">192.168.1.200<br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">10.23.0.2</span><br></div><div><br></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">$ dig some.domain @192.168.1.200 +short<br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">192.168.1.200<br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">10.23.0.2</span><br></div><div><br></div><div>(Local machine is on both the<span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> 10.</span> and <span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">192.168.</span> networks just fine)<br></div><div><br></div><div>Network setup inside the container (<span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">ip a</span>):<br></div><div><br></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> inet 127.0.0.1/8 scope host lo</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> valid_lft forever preferred_lft forever</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">121: eth0@if122: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> link/ether 02:42:ac:1c:00:02 brd ff:ff:ff:ff:ff:ff link-netnsid 0</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> inet 172.28.0.2/16 brd 172.28.255.255 scope global eth0</span><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"><br></span></div><div><span class="font" style="font-family:menlo, consolas, monospace, sans-serif;"> valid_lft forever preferred_lft forever</span><br></div><div><br></div><div>Can't say i'm entirely sure what "destination address of the query" is, and how / why it differs from the source address shown in the log. If it's using the return address it can see, it's possible it's using the <span class="font" style="font-family:menlo, consolas, monospace, sans-serif;">172.28</span> address, and hence isn't switching correctly?<br></div><div><br></div><div>How is the destination address calculated, is there something I can do to make this work as needed? Alternatively, is something in dnsmasq not playing correctly?<br></div><div><br></div><div>Thanks!<br></div><div><br></div><div>On Sun, 5 Apr 2020, at 21:49, Simon Kelley wrote:<br></div><blockquote type="cite" id="qt"><div><br></div><div><br></div><div>On 05/04/2020 14:48, Jake Howard wrote:<br></div><div>>><br></div><div>>> Dnsmasq uses the _destination_ address of the query. I'm not familiar<br></div><div>>> with Docker. Is it using NAT?<br></div><div>> <br></div><div>> Can't say i'm especially familiar with Docker's networking stack, but it<br></div><div>> definitely looks and feels like something NAT-ish to me!<br></div><div>> Interestingly enough, the log entry for where the query came from is<br></div><div>> correctly detected, but I guess it's not using that address to localise?<br></div><div>> <br></div><div>> eg:<br></div><div>> <br></div><div>> Apr 5 14:44:59 dnsmasq[505]: query[A] github.com from 10.23.0.23<br></div><div>> Apr 5 14:44:59 dnsmasq[505]: forwarded github.com to 1.0.0.1<br></div><div>> Apr 5 14:44:59 dnsmasq[505]: reply github.com is 140.82.118.3<br></div><div>> <br></div><div>> <br></div><div>> Are the addresses used in the log and the destination address different?<br></div><div>> Thanks,<br></div><div>> - Jake Howard<br></div><div><br></div><div><br></div><div>It uses the _destination_ address of the _query_ to localise, that's not<br></div><div>logged.<br></div><div><br></div><div><br></div><div>Simon.<br></div><div><br></div><div>> <br></div><div>> On Sat, 4 Apr 2020, at 19:01, Simon Kelley wrote:<br></div><div>>> On 31/03/2020 13:51, Jake Howard wrote:<br></div><div>>> > Hello!<br></div><div>>> > <br></div><div>>> > Had a breakthrough on what's going on, and it's down to a caveat I<br></div><div>>> > missed when reading the man page on localise-queries:<br></div><div>>> > <br></div><div>>> >> Return answers to DNS queries from /etc/hosts and *--interface-name*<br></div><div>>> > which depend on the interface over which the query was received.<br></div><div>>> > <br></div><div>>> > And of course, this issue has to do with docker. With Docker, even<br></div><div>>> > though the container is listening on 2 different interfaces, and 2<br></div><div>>> > different IPs, the inner container, and thus dnsmasq, only sees 1<br></div><div>>> > interface, with all addresses coming from it. Hence localisation isn't<br></div><div>>> > quite working.<br></div><div>>> > <br></div><div>>> > If I run dnsmasq with the exact same config but on the host, where it<br></div><div>>> > can see the different interfaces, works perfectly!<br></div><div>>> > <br></div><div>>> > Testing was done in 2.79 and 2.76, with a config file practically<br></div><div>>> > identical to your CLI arguments.<br></div><div>>> > <br></div><div>>> > Technically, there's not a bug here per-say, but it'd be really handy if<br></div><div>>> > there was a way of looking at the source IP when determining which<br></div><div>>> > record to return rather than just the interface?<br></div><div>>><br></div><div>>> Dnsmasq uses the _destination_ address of the query. I'm not familiar<br></div><div>>> with Docker. Is it using NAT?<br></div><div>>><br></div><div>>><br></div><div>>> Simon.<br></div><div>>><br></div><div>>><br></div><div>>> > <br></div><div>>> > Thanks!<br></div><div>>> > <br></div><div>>> > On Mon, 30 Mar 2020, at 20:42, Simon Kelley wrote:<br></div><div>>> >> On 28/03/2020 20:38, Jake Howard wrote:<br></div><div>>> >> > Hi,<br></div><div>>> >> > <br></div><div>>> >> > My intention is to have 1 dnsmasq instance, accessible over 2<br></div><div>>> interfaces<br></div><div>>> >> > (listening on all), and have the response to a query differ based<br></div><div>>> on the<br></div><div>>> >> > interface, and therefore its incoming IP. From what i've read, that's<br></div><div>>> >> > exactly what localise-queries is meant to do, but it doesn't<br></div><div>>> appear to<br></div><div>>> >> > be unless I put the entries into /etc/hosts directly.<br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> OK, what you're expecting to happen and what I'm expecting to<br></div><div>>> happen are<br></div><div>>> >> the same. That's good.<br></div><div>>> >><br></div><div>>> >> I just did a quick test, and it seems to work fine for me. The<br></div><div>>> >> example.com addresses are in /tmp/hosts.<br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> srk@holly:~/dnsmasq/dnsmasq$ src/dnsmasq -d --log-queries<br></div><div>>> >> --localise-queries -p 10000 --addn-hosts=/tmp/hosts<br></div><div>>> >> dnsmasq: started, version 2.81rc4-5-gd162bee cachesize 150<br></div><div>>> >> dnsmasq: compile time options: IPv6 GNU-getopt no-DBus no-UBus no-i18n<br></div><div>>> >> no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC<br></div><div>>> >> loop-detect inotify dumpfile<br></div><div>>> >> dnsmasq: reading /etc/resolv.conf<br></div><div>>> >> dnsmasq: using nameserver 127.0.1.1#53<br></div><div>>> >> dnsmasq: read /etc/hosts - 9 addresses<br></div><div>>> >> dnsmasq: read /tmp/hosts - 2 addresses<br></div><div>>> >> dnsmasq: query[A] example.com from 127.0.0.1<br></div><div>>> >> dnsmasq: /tmp/hosts example.com is 192.168.151.43<br></div><div>>> >> dnsmasq: /tmp/hosts example.com is 192.168.150.43<br></div><div>>> >> dnsmasq: query[A] example.com from 192.168.150.49<br></div><div>>> >> dnsmasq: /tmp/hosts example.com is 192.168.150.43<br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> If it's not working for you, that's a bug, but we need to find what it<br></div><div>>> >> is about your setup that tickles the bug.<br></div><div>>> >><br></div><div>>> >> Can you boil it down to the simplest configuration that displays the<br></div><div>>> >> problem, and also specify which version of dnsmasq you're using?<br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> cheers,<br></div><div>>> >><br></div><div>>> >> Simon.<br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> > <br></div><div>>> >> > Thanks,<br></div><div>>> >> > - Jake Howard<br></div><div>>> >> > <br></div><div>>> >> > On Sat, 28 Mar 2020, at 17:59, Simon Kelley wrote:<br></div><div>>> >> >> On 19/03/2020 21:47, Jake Howard wrote:<br></div><div>>> >> >> > Hello!<br></div><div>>> >> >> > <br></div><div>>> >> >> > Is `localise-queries` meant to work against entries added via <br></div><div>>> >> >> > `addn-hosts`? Querying a record returns both IPs, but always<br></div><div>>> in the<br></div><div>>> >> >> same <br></div><div>>> >> >> > order. The order is correctly fixed when the records are put in <br></div><div>>> >> >> > `/etc/hosts` directly.<br></div><div>>> >> >><br></div><div>>> >> >><br></div><div>>> >> >> Yes, localise-queries works with entries added via addn-hosts,<br></div><div>>> but it<br></div><div>>> >> >> doesn't have anything to do with the order that records appear,<br></div><div>>> so that<br></div><div>>> >> >> doesn't address your problem. What are you trying to achieve?<br></div><div>>> >> >><br></div><div>>> >> >><br></div><div>>> >> >> Simon.<br></div><div>>> >> >><br></div><div>>> >> >><br></div><div>>> >> >> > <br></div><div>>> >> >> > Config:<br></div><div>>> >> >> > <br></div><div>>> >> >> > ```<br></div><div>>> >> >> > localise-queries<br></div><div>>> >> >> > no-resolv<br></div><div>>> >> >> > cache-size=10000<br></div><div>>> >> >> > log-queries<br></div><div>>> >> >> > log-facility=/var/log/pihole.log<br></div><div>>> >> >> > local-ttl=2<br></div><div>>> >> >> > log-async<br></div><div>>> >> >> > server=8.8.8.8<br></div><div>>> >> >> > server=8.8.4.4<br></div><div>>> >> >> > server=1.1.1.1<br></div><div>>> >> >> > server=1.0.0.1<br></div><div>>> >> >> > interface=eth0<br></div><div>>> >> >> > server=/use-application-dns.net/<br></div><div>>> >> >> > <br></div><div>>> >> >> > addn-hosts=/etc/vpn-hosts.conf<br></div><div>>> >> >> > localise-queries<br></div><div>>> >> >> > <br></div><div>>> >> >> > ```<br></div><div>>> >> >> > <br></div><div>>> >> >> > This is from pihole, but AFAIK that shouldn't make a difference<br></div><div>>> >> if I'm <br></div><div>>> >> >> > modifying the config directly.<br></div><div>>> >> >> > <br></div><div>>> >> >> > Would appreciate some input, or being told i'm wrong!<br></div><div>>> >> >> > <br></div><div>>> >> >> > Thanks,<br></div><div>>> >> >> > <br></div><div>>> >> >> > - Jake Howard<br></div><div>>> >> >> > <br></div><div>>> >> >> > <br></div><div>>> >> >> > <br></div><div>>> >> >> > <br></div><div>>> >> >> > _______________________________________________<br></div><div>>> >> >> > Dnsmasq-discuss mailing list<br></div><div>>> >> >> > Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> >> >> > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>> >> >> > <br></div><div>>> >> >><br></div><div>>> >> >><br></div><div>>> >> >> _______________________________________________<br></div><div>>> >> >> Dnsmasq-discuss mailing list<br></div><div>>> >> >> Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> >> >> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>> >> >><br></div><div>>> >> > <br></div><div>>> >> > <br></div><div>>> >> > _______________________________________________<br></div><div>>> >> > Dnsmasq-discuss mailing list<br></div><div>>> >> > Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> >> > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>> >> > <br></div><div>>> >><br></div><div>>> >><br></div><div>>> >> _______________________________________________<br></div><div>>> >> Dnsmasq-discuss mailing list<br></div><div>>> >> Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> >> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>> >><br></div><div>>> > <br></div><div>>> > <br></div><div>>> > _______________________________________________<br></div><div>>> > Dnsmasq-discuss mailing list<br></div><div>>> > Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>> > <br></div><div>>><br></div><div>>><br></div><div>>> _______________________________________________<br></div><div>>> Dnsmasq-discuss mailing list<br></div><div>>> Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>>><br></div><div>> <br></div><div>> <br></div><div>> _______________________________________________<br></div><div>> Dnsmasq-discuss mailing list<br></div><div>> Dnsmasq-discuss@lists.thekelleys.org.uk<br></div><div>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss<br></div><div>> <br></div><div><br></div></blockquote><div><br></div></body></html>