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


"Randy Brick MacKenna" <randymackenna@xxxxxxxxx> wrote in message
news:1192544693.429382.78090@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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

What is the subnet of the XP stations? Does your Apache server have an
address internal to your network as well as the external address? If not
then you will always go out to the router and back in thus having potential
firewall issues. If you do have an internal address for your Apache server
then an entry in the hosts file pointing to the internal:32004 address will
keep it in house. The host file would need to be on all the XP clients. The
sequence is hosts file then DNS. If there is no internal IP then you can add
the line 192.168.10:32004 but you will most likely not notice any speed
difference between using a hosts file and the DNS server of choice.


.

Relevant Pages

  • Re: IP routing with remote DNS, but server & client on same subnet - how?
    ... One Linux server running Apache2 ... there" and on the internet, ... towww.mydomain.netand I'm redirected to my little Apache server. ... network, on one of my WinXP clients and I browse towww.mydomain.net, ...
    (comp.os.linux.networking)
  • Re: [SLE] trying to set up ip forwarding and masqurading...
    ... PPPOE performed by the Linksys router. ... i WANT all the internet to go through the server for various reasons. ... and i want to see how much bandwidth each person in the network is ...
    (SuSE)
  • Re: General Security Question
    ... >Just wanted to get some feeback on my server config. ... >security that I think it does? ... network looks like and against what do you want to protect yousrself. ... Then, are you up to known good versions of at least ssh, Apache and ...
    (comp.os.linux.security)
  • Re: Blocking Hackers Questions W2K
    ... > own server attached to the local network and the internet. ... Running Microsoft Office Update every week is a good thing to do also. ... Once you get the $50 linksys router you should download the free ...
    (alt.computer.security)
  • Re: Blocking Hackers Questions W2K
    ... > own server attached to the local network and the internet. ... Running Microsoft Office Update every week is a good thing to do also. ... Once you get the $50 linksys router you should download the free ...
    (comp.os.ms-windows.nt.admin.security)