The latest Pi-hole might not work properly on Jessie without some extra effort:
pi@noads:~ $ dnsmasq -v
Dnsmasq version 2.76
If devices receive DHCP IP details connected via copper but not if connected via WiFi, there is not allot you can do on the router I think ... I might be wrong.
If its a Raspi with WiFi, you could try connect both copper and Wifi if setup a bridge interface on Raspi but only if IP range/subnet are the same:
You can see which device IP is doing what DNS queries with below one (blocked queries show up red):
pihole -t
If you mean you configured the DHCP range to be "192.168.1.2 - .54", thats not going to work because the devices will be assigned an IP address thats on a different subnet as the router 10.10.10.1 and Pi-hole 10.10.10.13.
If devices need to communicate from one subnet to another, they will need another router again.
Better configure the DHCP range to be 10.10.10.20 -> 10.10.10.255 so they all live happily together on the same subnet (the 255.255.255.0 subnet mask bit when configuring IPv4 address).
Ps. dont forget to renew DHCP leases on the devices whenever you change DHCP settings.
Disconnect and reconnect devices from network to receive new DHCP details ... or reboot the devices ... or wait long time until the client lease expires 