httpd problem

Sean picasso@madflower.com
Fri, 21 Sep 2001 19:53:10 -0400 (EDT)


Can you get to your webserver from your internal machines, using the dhcp
address(144.x.x.x)? or just the internal (192.168.1.1)??

Cna you get to the outside from the internal machines?


On Sat, 22 Sep 2001, Marcel Kunath wrote:

> Hmmm, I figure it has to do with my dhcp setup and my domain but I could be
> wrong as I usually am. I got a list of about ten problems here which I am
> unable to solve and I am close to ditching suse and giving debian a shot on
> the server end. =) Got a spare drive so it can't hurt.
>
> I have two domain-names set up. The reason is I need one to get to the mail of
> my ISP and I have the other to set the domainname of my machines.
>
> server:
>
> # cat /etc/dhcpd.conf:
>
> ddns-update-style none;
> # I tried all three setups and I can't get to my own webserver
> option domain-name "mydomain.com nsw.bigpond.net.au";
> #option domain-name "nsw.bigpond.net.au";
> #option domain-name "mydomain.com";
> option domain-name-servers 61.9.192.13, 61.9.192.16, 35.8.2.41, 35.8.2.42;
> option broadcast-address 192.168.1.255;
> option subnet-mask 255.255.255.0;
> option routers 192.168.1.1;
> default-lease-time 600;
> max-lease-time 7200;
>
>
> host act {
>         hardware ethernet 00:02:DD:50:19:9B;
>         fixed-address 192.168.1.2;
>         option host-name "act";
> }
>
> subnet 192.168.1.0 netmask 255.255.255.0 {
>   range 192.168.1.20 192.168.1.30;
> }
>
> # cat /etc/resolv.conf
> search nsw.bigpond.net.au
> nameserver 61.9.192.13
> nameserver 61.9.192.16
> nameserver 35.8.2.41
> nameserver 35.8.2.42
>
> # route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 144.132.208.0   0.0.0.0         255.255.240.0   U     0      0        0 eth0
> 0.0.0.0         144.132.208.1   0.0.0.0         UG    0      0        0 eth0
>
>
> client:
>
> # cat /etc/resolv.conf
> search nsw.bigpond.net.au
> #search mydomain.com nsw.bigpond.net.au
> #search mydomain.com
> nameserver 61.9.192.13
> nameserver 61.9.192.16
> nameserver 35.8.2.41
> nameserver 35.8.2.42
>
> # route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
>
> Fact is I had webserver running on old suse 6.2 in very similar setup and it
> worked fine.
>
> m
> > > What do your internal
> boxes use as a nameserver? > > On Fri, 21 Sep 2001, Marcel Kunath wrote:
> >
> > > Hello,
> > >
> > > my problems just won't end these days...
> > >
> > > A real weird one. I got a domain. I use free dns from zoneedit.com. The box
> is
> > > on dhcp cable modem. I updated the zone to the latest IP. The update has got
> ten
> > > through all nameservers. Apache is running. The odd thing is any person outs
> ide
> > > my netwokr can get to it.
> > >
> > > I can get to it from my server and from machines inside my network via the
> > > internal IP. The box is also a firewall (but the problem also occurs when
> > > protection is turned off).
> > >
> > > I cannot reach the web server via its domain name from inside my network. An
> y
> > > other surfing using DNSystem is fine. Now this is ok as I could just use the
>
> > > internal IP to access it but I got virtual hosts set up as well and that
> > > basically should make this more complicated or impossible to set up.
> > >
> > > I just wonder why my network can't access it. The access and error logs don'
> t
> > > show anything. I know they work because they have few
> > > [Sat Sep 22 09:23:09 2001] [error] [client 144.132.40.143] File does not exi
> st:
> > > /usr/local/httpd/htdocs/scripts/..%5c../winnt/system32/cmd.exe
> > >
> > > in it. =)
> > >
> > > PS: BTW I did get on reiserfs list and worked further on my mkreiserfs /dev/
> hdb
> > > problem. I spend some time writing zeros to drives and etc. Eventually I
> > > figured out that the 8 gig seagate and 45 gig wdc drive didn't like being on
>
> > > same controller. Once I moved my drive into:
> > >
> > > /dev/hda seagate
> > > /dev/hdc wdc1
> > > /dev/hdd wdc2
> > >
> > > I could mkreiserfs /dev/hd(c,d) just fine.
> > >
> > > mk
> > > _______________________________________________
> > > linux-user mailing list
> > > linux-user@egr.msu.edu
> > > http://www.egr.msu.edu/mailman/listinfo/linux-user
> > >
> >
> > _______________________________________________
> > linux-user mailing list
> > linux-user@egr.msu.edu
> > http://www.egr.msu.edu/mailman/listinfo/linux-user
> >
>
>
> --
> Marcel Kunath
>
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
>
>  Montie House Network            Greater Lansing Linux Users Group
>   http://www.montiehouse.com      http://www.gllug.org
>
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> _______________________________________________
> linux-user mailing list
> linux-user@egr.msu.edu
> http://www.egr.msu.edu/mailman/listinfo/linux-user
>