Windows DHCP clients have to use FQDN to resolve local hosts

Hi,

All of my DHCP clients running Windows (Vista, 10) require the FQDN to resolve.  Here's my DHCP config:

admin@ispd-gw# show service dhcp-server
 disabled false
 hostfile-update enable
 shared-network-name vl100 {
     authoritative enable
     subnet 10.0.0.0/24 {
         default-router 10.0.0.254
         dns-server 10.0.0.254
         domain-name home.lan
         lease 86400
         start 10.0.0.1 {
             stop 10.0.0.253
         }
         static-mapping bbd-sw {
             ip-address 10.0.0.253
             mac-address 14:cc:20:59:db:28
         }
         static-mapping bedroom-tv {
             ip-address 10.0.0.87
             mac-address e4:7c:f9:6c:19:9d
         }
         static-mapping bru-asw {
             ip-address 10.0.0.248
             mac-address 14:cc:20:a0:c8:c0
         }
.......rest of my static mappings omitted....

admin@ispd-gw# show service dns forwardin
 cache-size 150
 listen-on eth0.100
 listen-on eth0.101
 options domain=home.lan
 options expand-hosts

If manaually enter the domain name under "Append these DNS suffixes (in order)" under the IP settings of each Windows client, then I can resolve without the FQDN.

I know I had this working in the past but just noticed today that is not working.

Thanks,

->g.