In order to restore pre-2.86 behaviour, the documentation explicitly directs you to
> (...) use the configuration --address=/example.com/1.2.3.4 --local=/example.com/ Note that address and local literals match, which they don't do in your configuration. But I agree that NXDOMAIN being answered from config is somewhat surprising. From the docs, I'd expected that request to have been forwarded upstream. However: On 28.06.24 15:38, Dimitry Andric wrote:
Sure, that also appears to work. I just don't know what the preferred syntax is for declaring hosts that have fixed IP addresses, as opposed to hosts that get addresses dynamically via DHCP.
If your use case is to provide names for hosts with static IP addresses, that should probably be tackled by using a hosts file, or by using host-records instead, e.g.: domain=example.com domain-needed host-record=foo,foo.example.com,10.1.2.3 host-record=bar,bar.example.com,10.1.2.4 Above 'domain-needed' would prevent that non-dot queries (e.g. for foo) would be forwarded upstream. Kind regards, Buck _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
