Hey Kevin, On Thu, 2020-04-23 at 13:21 +0000, Kevin Tedder wrote: > Now if I do the following: > ‘nslookup server1.at-home’, it resolves the IP address 192.168.1.67 > as I’d expect. > ‘nslookup MQTTBroker.at-home’, it resolves the IP address > 192.168.1.67 as I’d expect. > ‘nslookup 192.168.1.67’, it resolves the name of MQTTBroker.at-home, > not Server1.at-home as I wanted. Hmmm!!! > > Is this as designed or is it just bad luck on my part as to which > name is returned by the DNSMASQ? > Is there any configuration setting that can be made to control which > name takes preference? If not, can a mechanism/feature be added, such > as a priority system as to which is preferred.?
I'm not sure how you > added a fixed DNS ‘A’ record for a MQTT server but you may want to look at host-record. Quoting the man page: > Only the first address creates a PTR record linking the address to > the name. This is the same rule as is used reading hosts-files. -- > host-record options are considered to be read before host-files, so a > name appearing there inhibits PTR-record creation if it appears in > hosts-file also. It seems to be able to do what you want: ensure the PTR (address-to- name association) is registered as you want it to. Best, Dominik _______________________________________________ Dnsmasq-discuss mailing list Dnsmasqfirstname.lastname@example.org http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss