Can this be done?

  • Thread starter Thread starter Fernando Beleski
  • Start date Start date
F

Fernando Beleski

I have two 2000 servers:

Server1 is a web server (as server1.domain.com ) and has two NICs:
200.b.c.d, gateway 200.b.c.x (Cisco router to the internet) and 10.0.0.1,
gateway 10.0.0.138 (ADLS router, accessible as backup1.domain.com)

Server2 is the gateway for the LAN and also has two NICs: 10.0.0.2, gateway
10.0.0.138 (ADSL router, 200.m.n.o) and 192.168.0.2, no gateway, connected
to the LAN.

This server works as the gateway for the LAN, using NAT, so access to the
Internet for the LAN uses the ADSL router.

All the LAN computers use IPs like 192.168.0.x, gateway 192.168.0.2 and can
access the internet.

When a LAN computer opens http://server1.domain.com the traffic goes out
using the ADSL and comes back thru the Cisco, works fine.

A trace from a LAN computer looks like this:

c:\>tracert server1.domain.com

Tracing route to server1.domain.com [200.b.c.d] over a maximum of 30 hops:

1 10 ms 10 ms 10 ms 192.168.100.2 (server2)
2 10 ms 10 ms 10 ms 10.0.0.138 (ADSL router)
3 10 ms 10 ms 10 ms 200.m.n.o (ADSL router)

-------------------- internet --------------------------

8 10 ms 10 ms 10 ms 200.b.c.x (cisco router)
9 10 ms 10 ms 10 ms 200.b.c.d (server1)



The question is:

is there a way to avoid this 'long' route and make it use the local route?
How?

Or should I drop the NAT and use a software proxy?

Thanks

FB
 
It's not a routing issue, but a name resolution issue. If you local DNS
resolves the the name to the public address, it will go out to the Internet
via NAT. If you modify your local DNS so that it points to the private IP of
the web server, it will contact it directly on the LAN.

You can check this by doing

http://10.0.0.1
 
Back
Top