DNS not working on a TP-Link Archer C7 v5 in 19.07

Hi,

After upgrading to 19.07 tonight, none of my DNS queries are working.

$ host google.com 192.168.11.1
Using domain server:
Name: 192.168.11.1
Address: 192.168.11.1#53
Aliases: 

Host google.com not found: 5(REFUSED)

Oddly, queries start to work if I stop dnsmasq (via the init script) and start it on the command line (/usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf.cfg01411c -k -x /var/run/dnsmasq/dnsmasq.cfg01411c.pid -d). I saw in Upgraded TL-WDR4300 DNS no longer working that the recommended advice was to do a fresh install, which I have done.

Here's the debugging info requested in that thread.

dhcp.@dnsmasq[0]=dnsmasq
dhcp.@dnsmasq[0].domainneeded='1'
dhcp.@dnsmasq[0].localise_queries='1'
dhcp.@dnsmasq[0].rebind_protection='1'
dhcp.@dnsmasq[0].rebind_localhost='1'
dhcp.@dnsmasq[0].local='/lan/'
dhcp.@dnsmasq[0].domain='lan'
dhcp.@dnsmasq[0].expandhosts='1'
dhcp.@dnsmasq[0].authoritative='1'
dhcp.@dnsmasq[0].readethers='1'
dhcp.@dnsmasq[0].leasefile='/tmp/dhcp.leases'
dhcp.@dnsmasq[0].localservice='1'
dhcp.lan=dhcp
dhcp.lan.interface='lan'
dhcp.lan.start='100'
dhcp.lan.limit='150'
dhcp.lan.leasetime='12h'
dhcp.lan.dhcpv6='server'
dhcp.lan.ra='server'
dhcp.lan.ra_management='1'
dhcp.wan=dhcp
dhcp.wan.interface='wan'
dhcp.wan.ignore='1'
dhcp.odhcpd=odhcpd
dhcp.odhcpd.maindhcp='0'
dhcp.odhcpd.leasefile='/tmp/hosts/odhcpd'
dhcp.odhcpd.leasetrigger='/usr/sbin/odhcpd-update'
dhcp.odhcpd.loglevel='4'
lrwxrwxrwx    1 root     root            16 Jan  6 16:47 /etc/resolv.conf -> /tmp/resolv.conf
-rw-r--r--    1 root     root            32 Jan 12 09:52 /tmp/resolv.conf
-rw-r--r--    1 root     root           141 Jan 12 09:45 /tmp/resolv.conf.auto
==> /etc/resolv.conf <==
search lan
nameserver 127.0.0.1

==> /tmp/resolv.conf <==
search lan
nameserver 127.0.0.1

==> /tmp/resolv.conf.auto <==
# Interface lan
nameserver 8.8.8.8
nameserver 8.8.4.4
# Interface wan
nameserver (upstream dns #1)
nameserver (upstream dns #2)
search somecity.rr.com

Thanks in advance for any help you can provide.

Best,

Paul

Update:

The meaningful difference between the two commands is not that one is being run via an init script and the other is not, rather it is because one is running with -d and the other is not.

Adding -d to line 1066 (The one that starts with procd_set_param command) of /etc/init.d/dnsmasq results in DNS working correctly again.

Obviously this isn't a long-term solution, but I am mystified as to why it only works when debugging is enabled.