[Dnsmasq-discuss] dynamic DNS - maybe.... client provides name: xxxx

[Buck Horn]

On 18.12.24 01:37, Jack Snodgrass wrote:
>
> Dec 17 01:05:45 devbox dnsmasq-dhcp[1438630]: 3224099965 client
> provides name: ecoflow
> Dec 17 01:05:45 devbox dnsmasq-dhcp[1438630]: 3224099965
> DHCPREQUEST(HomeLan) 10.12.15.129 f4:f3:23:00:f4:28
> Dec 17 01:05:45 devbox dnsmasq-dhcp[1438630]: 3224099965 tags: HomeLan
> Dec 17 01:05:45 devbox dnsmasq-dhcp[1438630]: 3224099965
> DHCPACK(HomeLan) 10.12.15.129 f4:f3:23:00:f4:28 ecoflow
> Dec 17 01:05:45 devbox dnsmasq-dhcp[1438630]: 3224099965 requested
> options: 1:netmask, 3:router, 28:broadcast, 6:dns-serverwhen a device
> boots up and requests an ip address.
>
> (...)
>
> The device gets the 10.12.15.129 address assigned but the hostname
> ecoflow is not allocated anywhere.
> ping ecoflow or host ecoflow or ping ecoflow.mydomain.net, etc don't
> cause the 10.12.15.129 address to be resoved so all I get is:
> Host ecoflow not found: 3(NXDOMAIN)

By default, dnsmasq would already register client provided names, unless
configuration options would overwrite that name.

Your log not only shows the name as provided by your client, but also
demonstrates that dnsmasq has acknowledged ecoflow as name.
If ecoflow doesn't resolve, then either your client may have withdrawn
its lease, or the client that tried to resolve ecoflow is not talking
to  your dnsmasq for DNS.

In general, ping isn't adequate to analyse DNS issues, as it may use
other means to resolve names than just DNS, may also fail for reasons
unrelated to DNS, and doesn't provide important DNS details.

You should use DNS-specific tools like nslookup or dig, which will give
you more detailed information on a query.

Run from a client that fails to resolve ecoflow, what's the output of
the following commands:

nslookup ecoflow

nslookup ecoflow <dnsmasq-IP>

For the latter, substitute <dnsmasq-IP> with the IP address of the
machine hosting your dnsmasq.

Kind regards,
     Buck