Bob,

The way it works at least as I understand it is if a physical interface ip in your scenario is 10.0.0.1/24 DHCP can be enable in the interface to provide dhcp services for that particular network, that said, if your client wants to have another network routed within the firewall in the case of 10.1.0.1/24 and have dhcp services it would have to be in a different interface.

The question for you would be does your client already have a subnet with 10.1.0.1/24 somewhere in the network and wants firewall to be dhcp server for that subnet? if this is the case you cannot create a pool in firewall off the 10.0.0.1 interface to be a different network other than to be within the 10.0.0.1/24 network.

If your client wants to create another inside network to be routed in the firewall with 10.1.0.1/24 you could create subinterfaces and use 802.1q trunking, so you could have 10.0.0.1/24 say as inside1 for sub.interface name with security 100 and another subinterface named inside2 with IP 10.1.0.1/24 with same sec level of 100 as inside1, then you can have dhcp enabled on the two subinterfaces to service IPs on each subnet.

Now forget all above for a minute, if your client just wanst to change dhcp pool to be 10.1.0.1/24 then the inside interface ip address have to coinside with dhcp pool so your inside interface must change to 10.1.0.1/24 then create dhcp pool on interface.

hope this makes sence

Rgds

-Jorge