Personally I would turn off DHCP on your router and install it on your server, the best place for it.
How to install and configure, http://blogs.technet...erver-2012.aspx
Configuring the scope, http://technet.micro...y/dd759218.aspx
But I would also recommend doing a spreadsheet of how you want your scope laid out. Example, I am currently in the process of migrating a small company from SBS 2003 to Server 2012 with 365. I have created the scope for expansion and it is something like this.
192.168.0.1 to .9 - Servers
192.168.10.10 to 15 - Printers
192.168.0.250 to 192.168.0.254 - Switches and routers
Now, for the scope properties I would have the server pointing its DNS to its self along with all other servers and client (including the machine you want to join to the domain) The gateway to the router.
The important thing here though is to point the client to the server for DNS. Otherwise it not going to join.
I know how to navigate to the IPv4 properties, when I input this information and apply it, I'm unable to connect to the internet. See below.
On your original ipconfig the IP address is a 10.0.2.2 for the gateway, ow the IP is 192.168.1.19. They need to be on the same subnet for data to flow.