Dhcp/dns expandhosts not working after upgrade

I just upgraded to 24.10.6 (I believe from 24.10.5) and the automatic addition of the domain that dhcp.@dnsmasq[0].expandhosts='1' provides doesn't seem to be working.

Here's some (slightly modified) snippets:

# uci show dhcp p
dhcp.@dnsmasq[0]=dnsmasq
dhcp.@dnsmasq[0].domainneeded='1'
dhcp.@dnsmasq[0].localise_queries='1'
dhcp.@dnsmasq[0].rebind_protection='1'
dhcp.@dnsmasq[0].rebind_localhost='1'
dhcp.@dnsmasq[0].local='/lan/'
dhcp.@dnsmasq[0].domain='lan'
dhcp.@dnsmasq[0].cachesize='1000'
dhcp.@dnsmasq[0].authoritative='1'
dhcp.@dnsmasq[0].readethers='1'
dhcp.@dnsmasq[0].leasefile='/tmp/dhcp.leases'
dhcp.@dnsmasq[0].resolvfile='/tmp/resolv.conf.d/resolv.conf.auto'
dhcp.@dnsmasq[0].localservice='1'
dhcp.@dnsmasq[0].ednspacket_max='1232'
dhcp.@dnsmasq[0].expandhosts='1'
dhcp.lan=dhcp
dhcp.lan.interface='lan'
dhcp.lan.start='100'
dhcp.lan.limit='150'
dhcp.lan.leasetime='12h'
dhcp.lan.dhcpv4='server'
dhcp.lan.dhcpv6='server'
dhcp.lan.ra='server'
dhcp.lan.ra_flags='managed-config' 'other-config'
dhcp.wan=dhcp
dhcp.wan.interface='wan'
dhcp.wan.ignore='1'
dhcp.odhcpd=odhcpd
dhcp.odhcpd.maindhcp='0'
dhcp.odhcpd.leasefile='/tmp/hosts/odhcpd'
dhcp.odhcpd.leasetrigger='/usr/sbin/odhcpd-update'
dhcp.odhcpd.loglevel='4'
dhcp.odhcpd.piofolder='/tmp/odhcpd-piofolder'
dhcp.@host[0]=host
dhcp.@host[0].name='myhostname'
dhcp.@host[0].ip='10.3.1.1'
dhcp.@host[0].dns='1'
dhcp.@host[0].hostid='0101'
dhcp.@host[0].mac='AA:BB:C1:0A:4E:B8'
dhcp.@host[0].duid='000100001111111ae553e111111'
# dig bart

; <<>> DiG 9.20.21 <<>> myhostname
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7900
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;myhostname.                          IN      A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sat May 16 17:24:24 UTC 2026
;; MSG SIZE  rcvd: 33

root@brockway:/etc/config# dig myhostname.lan

; <<>> DiG 9.20.21 <<>> myhostname.lan
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19080
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;myhostname.lan.                      IN      A

;; ANSWER SECTION:
myhostname.lan.               0       IN      A       10.3.1.1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Sat May 16 17:24:29 UTC 2026
;; MSG SIZE  rcvd: 53

I was under the impression that the dhcp.@dnsmasq[0].expandhosts='1' line should be causing both of those dig results to return the same thing. This is working for AAAA records, though in the /tmp/hosts/odhcpd file, none of those names include the domain, whereas the /tmp/hosts/dhcp.cfg01411c has the .lan for each entry.

I'm not positive this was working before the upgrade, but I thought it was?

Is this how it really looks with the extra slashes?

No, that was leftover from when I first tried to post and the markdown formatter on here broke it. I'll fix above.

Interesting, I just noticed that as leases are renewed and they get added to /tmp/dhcp.leases, then those start resolving with dig myhostname.

Maybe this has always been like this and I'm just noticing because my update cleared out that file? Seems like it should work without that file, but maybe this is by design?