etc_dnsmasq_d Config not loading after updating to 6.1

Help
46

Thanks for confirming the fix!

Yes, this is a new feature only present in the other feature branch.

47

Hi there,

Problem solved with:

Core version is v6.1.2
Web version is v6.2.1
FTL version is v6.2.3 <- !!

All Seetings -> Misc -> misc.dnsmasq_lines: server & rev-server entries added
misc.etc_dnsmasq_d = disabled
dns.domain = empty

Problem exists when:
dns.domain = set to a value, in my case "home.local"

48

There seems to be an additional twist, probably triggered by requests arriving via a wg0 interface.

I just tried to access an internal website on a smartphone using Pi-hole via wireguard.
The lookup failed with NXDOMAIN (DNSSEC signed), while an earlier lookup today was successful:

~$ sudo grep "pihole-5 " /var/log/pihole/pihole.log

Jun 30 07:50:50 dnsmasq[16638]: 22887 10.47.17.2/48746 query[AAAA] pihole-5 from 10.47.17.2
Jun 30 07:50:50 dnsmasq[16638]: 22887 10.47.17.2/48746 regex denied pihole-5 is NODATA
Jun 30 07:50:50 dnsmasq[16638]: 22888 10.47.17.2/64877 query[A] pihole-5 from 10.47.17.2
Jun 30 07:50:50 dnsmasq[16638]: 22888 10.47.17.2/64877 forwarded pihole-5 to 192.168.2.1
Jun 30 07:50:50 dnsmasq[16638]: 22889 dnssec-query[DS] pihole-5 to 127.0.1.1#5335
Jun 30 07:50:50 dnsmasq[16638]: 22889 reply pihole-5 is no DS
Jun 30 07:50:50 dnsmasq[16638]: 22888 10.47.17.2/64877 reply pihole-5 is 192.168.2.55

Jun 30 16:48:05 dnsmasq[16638]: 25068 10.47.17.2/51548 query[A] pihole-5 from 10.47.17.2
Jun 30 16:48:05 dnsmasq[16638]: 25068 10.47.17.2/51548 cached pihole-5 is NXDOMAIN (DNSSEC signed)

As the grep implies, no other IPs have requested resolution of pihole-5 during that timespan.

(But there have been some requests for the FQDN `pihole-5.fritz.box`, each of them successful) 
~$ sudo grep pihole-5.fritz.box /var/log/pihole/pihole.log

Jun 30 07:49:57 dnsmasq[16638]: 22833 10.47.17.2/21566 query[A] pihole-5.fritz.box from 10.47.17.2
Jun 30 07:49:57 dnsmasq[16638]: 22833 10.47.17.2/21566 forwarded pihole-5.fritz.box to 192.168.2.1
Jun 30 07:49:57 dnsmasq[16638]: 22833 10.47.17.2/21566 reply pihole-5.fritz.box is 192.168.2.55
Jun 30 07:50:20 dnsmasq[16638]: 22886 10.47.17.2/44409 query[A] pihole-5.fritz.box from 10.47.17.2
Jun 30 07:50:20 dnsmasq[16638]: 22886 10.47.17.2/44409 cached-stale pihole-5.fritz.box is 192.168.2.55
Jun 30 07:50:20 dnsmasq[16638]: 22886 forwarded pihole-5.fritz.box to 192.168.2.1
Jun 30 07:50:20 dnsmasq[16638]: 22886 reply pihole-5.fritz.box is 192.168.2.55

Jun 30 16:04:51 dnsmasq[16638]: 24764 192.168.2.11/49141 query[A] pihole-5.fritz.box from 192.168.2.11
Jun 30 16:04:51 dnsmasq[16638]: 24764 192.168.2.11/49141 forwarded pihole-5.fritz.box to 192.168.2.1
Jun 30 16:04:51 dnsmasq[16638]: 24764 192.168.2.11/49141 reply pihole-5.fritz.box is 192.168.2.55

I am still using update/dnsmasq:

FTL
    Version is vDev-cc1c52d (Latest: null)
    Branch is update/dnsmasq
    Hash is cc1c52d2 (Latest: cc1c52d2)
49

Same issue here: 99-custom-local.conf with
address=/.domain.com/10.10.0.4
address=/domain.com/10.10.0.4

Pointing to my nginx (10.10.0.4) doesn’t work anymore. So I did this:

  1. Disabled misc.etc_dnsmasq_d
  2. Added lines to misc.dnsmasq_lines
  3. Delete „lan“ from dns.domain

Unfortunately no luck with Core v6.1.2 and FTL v6.2.3

Any ideas how to fix that?