Domains are not show local, but do show on internet

Hello,

I'm a newby on webhosting and apache. I've got my Virtual Host's working on
namebased. They can be accessed on the internet but when i type the domain
in the browser of the webserver i get an error that the server can not be
reached.

DNS is setup correct because i can connect to any other server. I need to
get this fixed because the webmail doesn't function at this moment.

Anybody an idea?

--

Met vriendelijke groet,
Michel van der Heijden (mvdh@emeni.nl)

On 2004-09-26, Michel <mvdh@emeni.nl> wrote:
> namebased. They can be accessed on the internet but when i type the domain
> in the browser of the webserver i get an error that the server can not be
> reached.

With so little information is quite difficult to make a diagnosis,
I think that there are various possibilites: 1. you "bound" the
server to the external IP only, so he refuses connection from the
loopback interface, 2. your connection to the internet is NATted
and this means that you can't connect using the external IP or your own
machine doesn't resolve addresses correctly. Only the first problem can
be solved by Apache configuration. So first check which one is the case.

Davide

--
It's no wonder they call it WinNT; WNT = VMS++;
-- Chris Abbey
%
Peace, Love and Compile the kernel...
-- Justin L. Herreman

> 2. your connection to the internet is NATted and this means that you can't
> connect using the external IP or your own
> machine doesn't resolve addresses correctly.

There's a router with NAT active indeed. Should i change that?

--

Met vriendelijke groet,
Michel van der Heijden (mvdh@emeni.nl)

On 2004-09-26, Michel <mvdh@emeni.nl> wrote:
> There's a router with NAT active indeed. Should i change that?

First check if that is _actually_ the case. If you don't mantain the
router I think that you should act in a different way. But, if that's
the case, the problem has nothing to do with the Apache configuration
and you should ask your ISP helpdesk or some other NG. And don't mess
the configuration of your router unless you know how to turn it back.

Davide

--
Here's your cable. We made it fifty feet long, just in case. In case
what, in case tectonic movement makes the serial ports farther apart?
-- Carl Jacobs

> First check if that is _actually_ the case. If you don't mantain the
> router I think that you should act in a different way. But, if that's
> the case, the problem has nothing to do with the Apache configuration
> and you should ask your ISP helpdesk or some other NG. And don't mess
> the configuration of your router unless you know how to turn it back.

I'm know my way in the hardware, it's just Apache that's new to me. ;-)
Thnx for the tip. I'll try it tomorrow....

--

Met vriendelijke groet,
Michel van der Heijden (mvdh@emeni.nl)

in 41567755$0$44109$5fc3050@dreader2.news.tiscali.nl Michel posted:

> Hello,
>
> I'm a newby on webhosting and apache. I've got my Virtual Host's
> working on namebased. They can be accessed on the internet but when i
> type the domain in the browser of the webserver i get an error that
> the server can not be reached.
>
> DNS is setup correct because i can connect to any other server. I
> need to get this fixed because the webmail doesn't function at this
> moment.
>
> Anybody an idea?

Using domain names to access a server on the LAN (or machine) you are
surfing from doesn't work right without tweaks to the browsing machine.
The DNS is basically telling your browser client to look at the web side
of your firewall. That is like trying to see your own eyeballs without
using a mirror. Any browser inside the LAN must use the local IP range
to see the Apache server.

It is for just this reason that I have an agreement with a friend to
allow ssh into each others servers to allow each of us to "go out, turn
around," and see what the outside of our firewalls look like.

To fix this locally the machine inside the firewall with the browser
must have a hosts file with the domain names pointing to the local IP
address for the server. Sort of a "locals only" DNS entry.

If this is all on one machine then you need to set the hosts file to
point the domains at "localhost" or 127.0.0.1
--
Stephen S.
-------------------------

> If this is all on one machine then you need to set the hosts file to
> point the domains at "localhost" or 127.0.0.1

Thank you. This was the trick for us. All works well. Thank you.

--

Met vriendelijke groet,
Michel van der Heijden (mvdh@emeni.nl)