Make sure (sub)domains served exclusively by dnsmasq are marked as
local=/tier1.internal/. That will prevent dnsmasq to forward any other
queries to upstream nameserver, which very likely does not know them.
That is if sshgw.tier1.internal has only A address, but is
forwarded further and t
This answer came just in time, as I have just returned from holiday and
was starting to consider if I should try out another dhcp-dns solution.
On 30.08.2024 Petr Menšík wrote:
Make sure (sub)domains served exclusively by dnsmasq are marked as
local=/tier1.internal/.
Thanks for pointing out
Hello,
We've run into a regression between 2.89 and 2.90 that was introduced
in
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=f5ef0f064c3f06b250a9eeda36dc239227658b00
which resolved the possible SIGSEGV reported in
https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2023q1/0169
