On Thu, May 12, 2022 at 02:55:01PM -0000, Rance Hall via Dnsmasq-discuss wrote: > I in the beginning of troubleshooting an issue with name resolution in dnsmasq > on a freebsd server. > I'm running dnsmasq 2.86 and I'm not able to resolve hostnames that are dhcp > clients. > This is a new development and may possibly be related to > a FreeBSD system upgrade from 13.0-RELEASE to 13.0-RELEASE-p11. > Example, my desktop machine is a dhcp client and is active on the > network, and can ping via hostname the firewall server that runs dnsmasq > which is assigned a static IP and reads /etc/hosts for static names and > /etc/resolv.conf.dnsmasq for upstream dns servers.However the firewall > cannot ping the client by name, despite a record for that host in the > dnsmasq.leases file.again, this is a new issue, and this used to work > when the server was originally setup. > I can prove that the leases database file is being written to by the > dnsmasq service as there are recent (read: from today) timestamps on > the file itself.I'd appreciate any pointers as I'm running out of things > to check and haven't found an obvious problem yet.Below is the startup > log entry from a dnsmasq server restart. Not sure if it helps, but I > didnt want to ask without trying to prove that I tried to fix it myself. > > <log_snippet> > May 12 09:21:16 icm dnsmasq[17586]: started, version 2.86 cachesize 150 > May 12 09:21:16 icm dnsmasq[17586]: compile time options: IPv6 GNU-getopt > no-DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth > cryptohash DNSSEC loop-detect no-inotify dumpfile > May 12 09:21:16 icm dnsmasq-dhcp[17586]: DHCP, IP range 192.168.19.75 -- > 192.168.19.125, lease time 12h > May 12 09:21:16 icm dnsmasq-tftp[17586]: TFTP root is /usr/local/tftp secure > mode > May 12 09:21:16 icm dnsmasq[17586]: using only locally-known addresses for > hallhome.private > May 12 09:21:16 icm dnsmasq[17586]: reading /etc/resolv.conf.dhcp > May 12 09:21:16 icm dnsmasq[17586]: using nameserver 71.10.216.1#53 > May 12 09:21:16 icm dnsmasq[17586]: using nameserver 71.10.216.2#53 > May 12 09:21:16 icm dnsmasq[17586]: using only locally-known addresses for > hallhome.private > May 12 09:21:16 icm dnsmasq[17586]: read /etc/hosts - 8 addresses > </log_snippet> > > Thanks for any assistance/pointers you can provide.
Partial quote of https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016349.html | Pattern seen on the mailing list is unawareness of | network-server-client-model. Expressing such problems is indeed hard, | but also the road to a solution. Know that you are the main stake holder | of the problem that you are facing. The highest reward for | finding a solution goes to you. Keep the eco system that you are | consulting healthy by sharing also your success stories. | | Avoid "DNS doesn't work", make it "My DNS client gets odd replies | from dnsmasq", "My DNS requests don't get forwarded" or another | non-generic issue. | | Use real DNS tools like `dig` or `host` instead of `ping`. Invest in understanding https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016349.html Visit https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q2/016358.html to get an idea how other people recieve what your email client is transmitting. > Rance No hard feelings Groeten Geert Stappers -- Silence is hard to parse _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
