IP routing with remote DNS, but server & client on same subnet - how?



I'm trying to understand how IP addresses and packet routing work on
my home network. Here's what I have set up:

1. Three WinXP clients
2. One Linux server running Apache2
3. A Linksys router, and cable modem

I have a website running on the Apache server, which is listening on
port 32004. The Linux machine is at a static ip address of
192.168.1.10

On the Linksys router, I have my cable modem IP address port-forwarded
to the Linux server's IP address.

I also have a domain name registered, e.g. www.mydomain.net

At my registrar, I tell them to redirect www.mydomain.net to my cable
modem IP address, port 32004. Everything works fine -- when I'm "out
there" (physically out of my house) and on the internet, I can browse
to www.mydomain.net and I'm redirected to my little Apache server.

Now, what I'm wondering is this: When I am physically on my home
network, on one of my WinXP clients and I browse to www.mydomain.net,
is the Linksys router, or Apache (or both) smart enough to say "wait a
minute -- the domain and client are on the same subnet, so let me just
route the packets completely within the 192. domain" (?)

I'm asking this because when I am on my home network I'd rather not
have HTTP being served out through my ISP's network, and back to me.
It would be much more efficient if that traffic just stayed on my
private network.

Also, if this traffic does indeed go back out through my ISP, is there
some way for me to configure (using a hosts file, or something) to say
"only when you are on your home domain, then www.mydomain.net should
map to 192.168.10:32004" (?)

Thanks,
Randy

.



Relevant Pages

  • Re: Networking is Messed Up
    ... Both our office network and my home network are simple "workgroups", ... Use a proxy server for your LAN. ... You may have winsock problem, WinSock is damaged or corrupt after disconnect ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networking is Messed Up
    ... DNS servers in the Local Connection IP Settings and the wireless disabled so ... Both our office network and my home network are simple "workgroups", ... Use a proxy server for your LAN. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Networking is Messed Up
    ... DNS servers in the Local Connection IP Settings and the wireless disabled so ... Both our office network and my home network are simple "workgroups", ... Use a proxy server for your LAN. ...
    (microsoft.public.windowsxp.network_web)
  • RE: Networking is Messed Up
    ... DNS servers in the Local Connection IP Settings and the wireless disabled so ... Both our office network and my home network are simple "workgroups", ... Use a proxy server for your LAN. ...
    (microsoft.public.windowsxp.network_web)
  • Re: [fw-wiz] home net security (was Re: 802.11b and IPSec)
    ... of data on their home network is- or who underestimates it. ... > services from those hosts). ... I don't feel I need 3DES, it *is* a home network after all, and the host ... more about that when I summarize the responses. ...
    (Firewall-Wizards)