httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoe Ballz" <>
Subject Re: [users@httpd] problem displaying website.
Date Wed, 25 Aug 2004 00:04:18 GMT
Its not the routers configuration (probably) - its the routers capability. Most cheaper routers
cannot handle the equivalent of a hosts file themselves. Only the top end routers (as far
as I am aware) can do that kind of thing. If the hosts file works, then your problem is exactly
what I said. If a router can route external port 80 to an internal port 80, most cannot route
an internal port 80 to another internal port. If your router cannot do this and it is not
practical for you to update the hosts files on each machine, then I would suggest you look
into getting a DNS proxy server that you can set dns overrides to run inside your network.
I know there is software capable of what you require, but I have not used it myself so cannot
recommend one.

If you are using windows on the other machines - isn't there a way to synchronise files between
machines so you only need to edit 1 and the other follow suit? (actually - if someone knows
how to do this please let me know anyway =-) )

Good luck

Zoe - Website Hosting for the Transgendered Community
  ----- Original Message ----- 
  From: mbastreak 
  Sent: Wednesday, August 25, 2004 12:51 AM
  Subject: RE: [users@httpd] problem displaying website.

  Sure the hosts file works great, but there is still a problem with having to update hosts
files every time something changes. I have the same setup at home, except for a different
router and it works great. Which leads me to believe that something in how the router's is
configured that is making it not allow the local computers to access the website like normal.

  See, I can do an nslookup on the domain name and get the correct Outside IP address, but
if I try to go to the website by the convetional way it dies. Another thing is the router
has a built in configuration website, that resides on port 8100 on both the outside world,
and the inside world and it works fine by going to the ip address of the router and port 8100
so there has to be something to do with the firewall and the router's configuration.

    -----Original Message-----
    From: Zoe Ballz []
    Sent: Tuesday, August 24, 2004 6:38 PM
    Subject: Re: [users@httpd] problem displaying website.

    Have you tried the HOSTS file like I said before? What happened? Please give exact examples
of the addressed you are referring to. When you say "resolve then name correctly" what exactly
did it resolve to? If you don't want to publicise the details on the forum, email me direct.
This is a network issue and probe not an Apache issue so sorry to those people who think this
is "off subject".

    Zoe - Website Hosting for the Transgendered Community
      ----- Original Message ----- 
      From: Patrick O'Neal 
      Sent: Tuesday, August 24, 2004 3:23 PM
      Subject: RE: [users@httpd] problem displaying website.

      Well since the name is resolving correctly on all of the client computers on the LAN,
which they get all of there DNS info from the Router, I would say that DNS is fine. I believe
the real problem must be in how the router's firewall is handling the traffic. I am just not
sure why the LAN computers get a timed out error when they try to go to the website by its
real name or its real outside IP address but when I put in the address of the local server
it works great. It really makes me believe that is a firewall issue.
        -----Original Message-----
        From: Jeroen van Meeuwen []
        Sent: Tuesday, August 24, 2004 8:25 AM
        Subject: RE: [users@httpd] problem displaying website.

        And how about the DNS relay server on your router?

        Kind regards,


          From: mbastreak [] 
          Sent: dinsdag 24 augustus 2004 15:01
          Subject: RE: [users@httpd] problem displaying website.

          No, there is no proxy server. The Router does everything. What is interesting is
that when I ping the website from any of the clients on the LAN they resolve the name correctly
and even if I type in the direct WAN address of the router I still can't bring up the webpage,
only when I type in the direct address of the server can I bring up the website.

            -----Original Message-----
            From: Jeroen van Meeuwen []
            Sent: Tuesday, August 24, 2004 6:16 AM
            Subject: RE: [users@httpd] problem displaying website.

            I'm sorry, first reply didn't make any sense...

            I'm presuming you have a proxy server (configured on all clients on your LAN):

            Bypass local addresses

            Then, I'm presuming you have a router which forwards DNS requests:

            Configure the router NOT to query outside-world DNS servers when clients try and
resolve your domain names.
            You're router has a priority in resolving DNS queries (weither from clients or
from itself), use this priority. Namely the hosts file on your router could help you. Most
routers though have a DNS relay server, which could be configured to answer without relaying
the client's requests

            Kind regards,



            From: Zoe Ballz [] 
            Sent: dinsdag 24 augustus 2004 10:51
            Subject: Re: [users@httpd] problem displaying website.


              From the outside world, your site has an IP. This is the IP of your ROUTER and
not the server itself, but your router passes the requests through to your server, thus the
server appears to work ok.

              From inside your network, DNS will give other machines the SAME IP and point
people to your router. Your router probably doesn't know what to do with the requests and
ignores them. From an internal network the IP of your server will be different to the outside

              Try setting up a HOSTS file on each machine on your network. You should find
details on how to do this in the documentation of the operating systems on the other machines.
e.g. on windows 98 you edit a file called HOSTS in the windows directory, and put in an entry
like the following:


              where 123.123 etc is the LOCAL IP of your server.

              This will cause the machine in questions to bypass the DNS lookup for the domain,
and override it, sending the request to the IP you specify (i.e. your local IP of your server)

              I hope this helps

              All the best


     - Website Hosting for the Transgendered Community
                ----- Original Message ----- 
                From: mbastreak 
                Sent: Tuesday, August 24, 2004 2:47 AM
                Subject: [users@httpd] problem displaying website.

                I have a problem, that I am sure I have seen posted to this list before but
                I can't seem to find the answer and I sure don't know how to search for it
                using google, as it is a complicated question to ask but requires a simple
                answer. Anyway to get down to the details:

                OS: windows 2000 Workstation
                BUILD: Standard install from Apache website, installed as an .msi file and
                no extra modules
                CAYMAN Netopia 3564 Business Class DSL router and DSL running DHCP and NAT.
                Firwall: a pinhole setup to allow TCP ports 80-85 to the internal webserver
                on the internal port of 80.

                Problem: The website works great to the outside world everyone can see it
                and nothing is wrong, however when it comes to anyone on LAN, they can not
                see it unless type in the IP address of the computer hosting the website.
                know I have seen an answer to this before so please can someone refresh my


                Patrick O'Neal

                The official User-To-User support forum of the Apache HTTP Server Project.
                See <URL:> for more info.
                To unsubscribe, e-mail:
                   "   from the digest:
                For additional commands, e-mail:

View raw message