You probably mean 'PPTP' VPN.
This type of VPN works by creating a virtual network adapter on the client side. Any network adapter, virtual or not, can/will have routing table entries and this controls where traffic goes.
All outgoing traffic is checked against the routing table. Routing table entries with higher or more specific subnet masks are chosen to send traffic through before ones with lower or less specific subnet masks. The subnet mask of 192.168.0.X is 255.255.255.0, or /24. The default gateway, which collects all traffic not picked up by anything else, has a "subnet mask" of 0.0.0.0, or /0.
By virtue of assigning an IP address and subnet mask to an adapter, you automatically get a free route. Let's say your home router gives one of your adapters an IP address of 10.1.1.40, and a subnet mask of 255.255.0.0 (which equals /16). This inherently means that any traffic that goes out of that adapter can reach anywhere on 10.1.X.X. So a route table entry is generated to that effect. Outgoing traffic is checked against the routing table and if it's going to somewhere else in 10.1.X.X, it will NOT go through your default gateway which is a /0.
Hopefully by now, you can see that if you are sending traffic to an IP not within by your VPN adapter's subnet, it's going to go through the default gateway and therefore through the whole Internet.
Really the only way to accomplish what you are trying to do is:
- Configure the VPN on the server side to tell clients to use the VPN adapter as the default gateway. This will cause all client traffic to go through your VPN.
- Configure the VPN on the server side to tell clients to use a server within the VPN for DNS
- Configure some IPTables firewall rules that will catch outgoing traffic on the public IP's of your servers and redirect them to the appropriate VPN-reachable IPs. If clients are using your VPN as the default gateway you might not really need to do this, but it would ensure no traffic leaks outside of your VPN if clients are only trying to reach internal addresses.
- You also can run a separate DNS server, or a separate DNS domain, that is reachable only within the VPN and that resolves names for clients on the VPN, to internal VPN addresses instead of public IP addresses.
Another side note: VERY BAD IDEA to use 192.168.0.X, or 192.168.1.X for a company VPN - because this might conflict with common IP ranges setup for home routers. You should change it to something uncommonly used at home like 192.168.88.X.