Is having duplicate networks possible?

[mcast999]

Please refer to the picture I added. I have a situation where in ZONE1 and ZONE2 NEED to have the exact same IP address schemes. 

ZONE1 and ZONE2 connect to SW1 via point2point connections. The idea is that host connected to SW1 in the 10.0.0.1 need to access 192.168.1.1 in ZONE1. But also, 10.0.0.1 needs to contact 192.168.1.1 on ZONE2. Is this possible to configure? My boss says it is and that he has seen it before but I dont see how. On SW1 i created static routes (ip route 192.168.1.1/24 172.255.255.2 name ZONE1) and (ip route 192.168.1.1/24 172.255.254.2 name ZONE2). When I ping 192.168.1.1  from 10.0.0.1 it only pings ZONE1. I need to shut down port g0/0 on SW1 and try the ping again and of course then it goes to ZONE2. I need a way to tell 10.0.0.1 I need 192.168.1.1 in ZONE1 or ZONE2.

[marce1000]

  - @mcast999   Such requirements are invalid and all systems on the intranet must have unique ip addresses,

  M.

[MHM Cisco World]

using DNS and dual NAT but that so so hard to manage 

sorry 

MHM

[Joseph W. Doherty]

Is having duplicate networks possible?

Correct answer is: "maybe" or "it depends".

This is also why the first two replies appear to contradict each other.

As to how it might be done, in your topology also depends on what your requirements are.  From a SW1 connected host, are the two physical 192.168.1.1 hosts logically one host or two hosts?  If logically one host, do they mirror each other, including supporting stateful in-flight recovery?  If two hosts, if you ping 192.168.1.1, how would you know which one should be pinged or which one would be replying to the ping?  You yourself describe wanting to ping a specific zone 192.168.1.1 host.  So, what ping option allows you to ping a specific host IP, when as noted in the first reply, IPs are supposed to be unique?

Second reply describes using dual NAT, yup, but exactly how it might be is an "it depends", and how hard to manage would also be "it depends".