[Dnsmasq-discuss] Forwarded TCP queries not obeying --server=/domain/server arguments

[Hollett, Nicholas]

In upgrading from 2.49 to 2.62, TCP queries which are received are blindly
forwarded to the default server, not the one defined for the specific
domain specified using --server arguments to dnsmasq. See the below output:

# dnsmasq -d -q -a 172.16.0.1  --server=/zoidberg.internal/172.16.0.30



dnsmasq: started, version 2.62 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6
no-Lua TFTP conntrack
dnsmasq: using nameserver 172.16.0.30#53 for domain zoidberg.internal
dnsmasq: reading /etc/resolv.conf
dnsmasq: using nameserver 192.168.137.8#53
dnsmasq: using nameserver 172.16.0.30#53 for domain zoidberg.internal
dnsmasq: read /etc/hosts - 8 addresses
dnsmasq: forwarded query to 192.168.137.8

This happens when requesting using dig:
# dig @172.16.0.1 +tcp _ldap._tcp.zoidberg.internal SRV
which then fails to return anything because the upstream DNS doesn't know
about zoidberg.internal. However, when removing the +tcp option:

dnsmasq: query[SRV] _ldap._tcp.zoidberg.internal from 172.16.0.1
dnsmasq: forwarded _ldap._tcp.zoidberg.internal to 172.16.0.30

and I get the correct result in dig.

This configuration was working fine with dnsmasq 2.49.

Kind regards,
Niax
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20121207/6444471d/attachment.html>