Hostname resolving - hit and miss

Super weird behavior on Linksys EA8300 running latest OW 24.10.1.

I have static leases for everything on the local/private net and a PiHole serving DNS. DHCP is on the router @ 192.168.1.1 and NOT the PiHole. Router forwards DNS to PiHole. That part is working well EXCEPT for one little idiosyncrasy. That is, some Hostnames resolve and some do not despite all being on the same hardwired subnet.

I can paste a Hostname from OW's Static Lease listing into OW's PingIPv4 diagnostic tool and it'll return a nice fast ping set. I can grab another Hostname and it'll respond with "bad address". Their example dhcp configs are shown below. The behavior appears ... moody. :face_in_clouds:

config host
	option name 'Chromecast-LivingRoom'
	list mac 'REDACTED'
	option ip '192.168.1.9'

config host
	option name 'LaserPrinter'
	list mac 'REDACTED'
	option ip '192.168.1.4'

config host
	option name 'WDTVLive'
	list mac 'REDACTED'
	option ip '192.168.1.5'

Testing via the Windows terminal, Ping results will show ".lan", ".local" or nothing at all appended to the Hostnames. But what was "bad address" above will yield a good Ping in the CLI Term. :thinking:

Attempts to reach the http server of a given Host device via browser rarely works. Instead, yielding search engine results from the web. Direct IPv4 access to a device's http service does work however

Something's obviously not configured correctly and I'm not figuring it out on my own thus far.

Finally, a special/peculiar case. Our LaserPrinter is connected via WLAN and is the only device on the BG WiFi channel. Access to the printer from Hosts works as expected via direct IP address. In no case however can I access it via its Hostname or permutations thereof. In the Associated Stations list of the Wireless page, each Host has ".lan" appended to its name EXCEPT for LaserPrinter. Hmm...

Advise Plz.

TY

This might be your problem. mac is an option, not a list.
See:
Configuring Static Leases

That's peculiar given that it is Luci who is writing the actual dhcp file.
AFAICT - the Configure Static Leases page does not address this option/list issue. Given that Luci is writing the dhcp file I'm not sure where to go next.

I often use static leases and have never had your problem. I don't use Luci and always add the mac as an option.... So I think it does address the issue. Note, I did say it might be your problem.

Why don't you try editing the config file to option instead of list?
Nothing to loose :hot_beverage:

DHCP and DNS configuration /etc/config/dhcp
This instruction page follows what I find Luci is writing and shows the MAC field as a list parameter rather than option yet I can certainly see why, given that MAC is not a required field (according to the table), the entry would reflect that. Hmm... The MAC parameter does allow for multiple, space-separated addresses, i.e., an address list. However, with only a single MAC address to assign to a Hostname perhaps option would work as well.

Diving in the shallow end... and hit the bottom. No change in results. Darn it.

SOLUTION -
Enabling "Forward/Reverse DNS" option while in the Edit static lease page for each Host entry resolves (pun intended) the issue.

That link is incorrect and even contradicts itself, right at the top:

uci add dhcp host
uci set dhcp.@host[-1].name="mylaptop"
uci set dhcp.@host[-1].mac="11:22:33:44:55:66"
uci set dhcp.@host[-1].ip="192.168.1.22"

The syntax uci set ... is to "set" an option.
The syntax uci add_list ... is to "add" a list.

On top of that, if you had more than one mac address associated with one ipv4 address, then arp would fail.

I simple words, arp would go like this, eg:

Who has 192.168.1.10?
I do! (says every mac address in the list).
Ooops. Where to send these packets?

This is why baldness is so common. Pulling our hair out trying to figure this all out. LOL
I did reconfigure my 3D printer's RPi device to use multiple MACs; either LAN or WLAN connection depending on what I'm doing with it. It'll be interesting to see how it behaves upon next use.

I do wonder how DHCP will behave in this scenario. Will it simply ignore requests once the reserved IP has been assigned to one of the listed MACs? Hmm...

Anyway, thx for helping me get sorted out on this. Nice that it went quickly.

The wireless interface and ethernet interface would normally both be on the same bridge device. It is the bridge device that has an ip address, be it static, static lease or normal dhcp (dynamic lease).
You can have multiple ip addresses for one mac address, but you cannot have multiple mac addresses for one ip address - that breaks arp.

The scenario is invalid. But if it was valid, it would cause dhcp to fail.

According to the dnsmasq man page, you can only assign one mac address to a static lease.
The uci config is used on startup of dnsmasq to generate a dnsmasq.conf file. What does it do with the list entry created by Luci? probably takes the first mac in the list and ignores the other(s)...
Look at the --dhcp-host option in the man page:
Dnsmasq man page

The dnsmasq conf file is in /tmp/etc and is of the form dnsmasq.conf.cfgxxxxxx

Please show the output of:
cat /tmp/etc/dnsmasq.conf.cfgxxxxxx, substituting the actual file name.