Home network acting a bit silly

Hello,

I currently have this problem where I am running a linux server behind
a router with its ip DMZ'd. Users from outside of the network can
access the server by DNS or IP, but within I can only see it by its
local internal IP.

Is there anyway to fix this?

Kent

(E-Mail Removed) wrote:
> Hello,
>
> I currently have this problem where I am running a linux server behind
> a router with its ip DMZ'd. Users from outside of the network can
> access the server by DNS or IP, but within I can only see it by its
> local internal IP.
>
> Is there anyway to fix this?

Option 1:
Put /etc/hosts entries on every box that points to your internal IPs.
(If you've got Windows, it's \Windows\System32\drivers\etc\hosts IIRC.)

Option 2:
Install and configure an internal DNS server that returns internal IPs
for internal names and forwards requests for external names.

Option 1 is the low-tech way for small networks.

Allen Kistler wrote:
>
> Option 1:
> Put /etc/hosts entries on every box that points to your internal IPs.
> (If you've got Windows, it's \Windows\System32\drivers\etc\hosts IIRC.)
>
> Option 2:
> Install and configure an internal DNS server that returns internal IPs
> for internal names and forwards requests for external names.
>
> Option 1 is the low-tech way for small networks.

Allen,

The problem with 1) is that I am not trying to just manually associate
the domain with that server, so that I can access it easily. The
problem is that I need to be able to access the external IP,
internally. I was able to do this around a week ago, but all of a
sudden that changed.

The problem with 2) is similar to the problem of one.

Is there any way to just manually force the external IP to be
associated with that internal one? As it is now, outside users are sent
to it because of the DMZ, but not internal ones.

Kent

(E-Mail Removed) wrote:
> Hello,
>
> I currently have this problem where I am running a linux server behind
> a router with its ip DMZ'd. Users from outside of the network can
> access the server by DNS or IP, but within I can only see it by its
> local internal IP.
>
> Is there anyway to fix this?
>
> Kent

I was thinking, is there perhaps a way to manually map the route?

traceroute to **.**.***.*** (**.**.***.***), 64 hops max, 40 byte
packets
1 * * *
2 * * *
3 * * *
4 * * *
etc.

Kent

On 15 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, (E-Mail Removed) wrote:

>Allen Kistler wrote:

>> Option 1:
>> Put /etc/hosts entries on every box that points to your internal IPs.

>> Option 2:
>> Install and configure an internal DNS server

>The problem with 1) is that I am not trying to just manually associate
>the domain with that server, so that I can access it easily. The
>problem is that I need to be able to access the external IP, internally.

Why? What (other than IP address and other variables in the IP and TCP
header) do you expect to be different?

>I was able to do this around a week ago, but all of a sudden that changed.

That would be a routing issue most likely - and changes don't happen by
themselves. What did you change?

>Is there any way to just manually force the external IP to be
>associated with that internal one? As it is now, outside users are sent
>to it because of the DMZ, but not internal ones.

You've done that - Now the question is what has changed. Does the server
know how to send packets back out to the router to get back to your
internal systems? Or is it trying to send the replies direct, and your
system is ignoring them because you aren't talking to "this internal
address", but are trying to talk to "that external address". They
don't match (and you may have firewall issues as well), and the conversation
never gets established.

If your server and client are capable, run a packet sniffer on each, and
see where the packets are [not] going.

Old guy