I wouldn't expect the dnsmasq DHCP server to return these hostnames at
all, so something unexpected is happening. Are sure the clients aren't
doing a reverse-DNS lookup on their assigned address, or something similar?
Setting --log-queries and --log-dhcp and posting the results (or sending
them to me) may help to make things clearer.
Simon.
On 01/08/2022 00:32, Jack Bennett via Dnsmasq-discuss wrote:
synth-domain and known-hosts don't create the expected dhcp hostname for
the DHCP ACK.
With the use of *--synth-domain=thekelleys.org.uk
<http://thekelleys.org.uk/>,192.168.0.50,192.168.0.70,node-** and
*--dhcp-host=00:00:5e:00:53:af,192.168.0.55,24h* results in a lease
of*node-192-168-0-55.thekelleys.org.uk
<http://node-192-168-0-55.thekelleys.org.uk/>* instead of the expected
*node-5.thekelleys.org.uk <http://node-5.thekelleys.org.uk/>* in the
DHCPACK response.
The same goes for *--dhcp-host=00:00:5e:00:53:af,24h *the lease hostname
is *node-192-168-0-50.thekelleys.org.uk
<http://node-192-168-0-50.thekelleys.org.uk/>* instead of:
*node-0.thekelleys.org.uk <http://node-0.thekelleys.org.uk/>*
The dns seemed to resolve as expected for either address, my issue is
with the dhcp packet hostname value.
--
Jack Bennett
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
