yuk... as Nick pointed out the below is totally wrong (amongst other problems) - trying to assign dhcp addresses outside the subnet
Have to assume you did a copy-and-paste and this is not a typo

Doesn't dnsmasq run any verification checks before it runs? - if not, that is really bad - should not even start with something configured like that... Is there no dnsmasq utility either to verify the configuration files used by dnsmasq..

Don't use dnsmasq here (and seeing this really glad not using it), but the following

Use several VLANS here and tried to configure an incorrect range for dhcpd on a VLAN
It would not start and spit out this helpful error message

-- Unit dhcpd.service has begun starting up.
Oct 18 11:37:25 karien.sraellis.com dhcpd[32382]: Internet Systems Consortium DHCP Server 4.2.5
Oct 18 11:37:25 karien.sraellis.com dhcpd[32382]: Copyright 2004-2013 Internet Systems Consortium.
Oct 18 11:37:25 karien.sraellis.com dhcpd[32382]: All rights reserved.
Oct 18 11:37:25 karien.sraellis.com dhcpd[32382]: For info, please visit https://www.isc.org/software/dhcp/
Oct 18 11:37:25 karien.sraellis.com dhcpd[32382]: bad range, address 192.168.9.64 not in subnet 192.168.8.0 netmask 255.255.255.0