Koozali.org: home of the SME Server

Virtual Hosts not connecting

Scott

Virtual Hosts not connecting
« on: August 23, 2003, 04:24:01 AM »
HI,

No one in the general forum responded to my question.
I have a netgear RT314 router on the backside of that
is my SME5.6 server set at server only.

I can access my primary domain from the internet
but I can not access any of the virtual domains
from the internet.

All virtual domains come up just fine when I point
my browser to them on the local net, however
only page not found errors come up on the
internet.

Is this a router issue? It seems to me that if my
primary domain can be accessed from the internet,
and the virtual sites work fine on the local net, then
they should also work fine from the internet.

Any Clues would be appreciated.

Thanks in advance. Scott.

Guck Puppy

Re: Virtual Hosts not connecting
« Reply #1 on: August 24, 2003, 12:12:54 AM »
Scott wrote:

> I can access my primary domain from the internet
> but I can not access any of the virtual domains
> from the internet.
Your virtual domains must have DNS records available to the internet that point to the IP address of your SME server. Who provides your internet available DNS server?

> All virtual domains come up just fine when I point
> my browser to them on the local net, however
> only page not found errors come up on the
> internet.

Are they page not found (404 errors) or 'server could not be found' errors?

If they are 'server could not be found' see my point about DNS above.

G

mark

Re: Virtual Hosts not connecting
« Reply #2 on: August 24, 2003, 11:06:09 AM »
presumably you have checked that the virtual domains resolve properly to your external ip?

Mark

Scott

Re: Virtual Hosts not connecting
« Reply #3 on: August 25, 2003, 04:37:43 AM »
Yes,

I had one site setup so that
the dns was pointing to the
name server on the machine.
It was resolving to the local
ip as opposed to the net ip.

Saturday, I installed a second nic
and took the server off of the router
and connected it directly to the modem.

After I reconfigured it to gateway and
server, I logged on through dial up.
While I wasn't able to surf to the site
using a dialup connection, I did recieve
the correct ip when I pinged the virtual
domains.

So on Monday when I go into work,
I will check the virtual sites and
see if they are resolving properly.

Thanks for the response and
the help.

Scott

Re: Virtual Hosts not connecting
« Reply #4 on: August 25, 2003, 05:30:44 AM »
Hi all,

Thanks a bunch for helping me with thsi
issue. I succesfully sent an email
to one of my virtual domains which
indicates that everything is resolving
correctly now.

Scott

Scott

Re: Virtual Hosts not connecting
« Reply #5 on: August 25, 2003, 06:56:16 PM »
OK,

I checked and the site are not
working. Even the Primay is
down.

Question, Do I need to set the
hosts to global instead of
local?

Thanks

Scott.

Guck Puppy

Re: Virtual Hosts not connecting
« Reply #6 on: August 26, 2003, 12:40:36 AM »
Scott wrote:
> Question, Do I need to set the
> hosts to global instead of
> local?

Guck Puppy wrote:
>Your virtual domains must have DNS records available to the
> internet that point to the IP address of your SME server.
> Who provides your internet available DNS server?

Who provides your internet available DNS server? The answer seems to be "You are attempting to host DNS yourself."

Understand that just wishing that your SME server will function as a public DNS server (one that is 'available to the internet') will not make it so. Out of the box, the DNS server on SME is NOT 'available to the internet'. Thus, if this is the only place you are making your DNS records, no-one but you, locally is going to know anything about it.

I have made my 5.6 box a Public DNS server following the excellent how-to available at :
http://www.sglinuxos.org/modules.php?name=Content&pa=showpage&pid=3

What's your situtation Scott - where on the net are your DNS records?

G

Scott

Re: Virtual Hosts not connecting
« Reply #7 on: August 26, 2003, 01:25:54 AM »
Gary wrote:

Who provides your internet available DNS server? The answer seems to be "You are attempting to host DNS yourself."
What's your situtation Scott - where on the net are your DNS records?

I have dns service with bulkregister. and yes the domain is set to
the correct ip address. Funny thing is the primary domain was working
when I had the server set to just server and connected through the
router. After I set the machine to be a server and gateway, and
connected it directly to the modem the primary stopped working.

The other odd thing is that I can recieve email. I sent an email
to myself this morning after I found that the site was not
comming up. I just logged into webmail and seen that
I recieved it at 8:52:57 am. So somehow, dns is working
for email but not for webhosting.

Gary also wrote:
Understand that just wishing that your SME server will function as a public DNS server (one that is 'available to the internet') will not make it so. Out of the box, the DNS server on SME is NOT 'available to the internet'. Thus, if this is the only place you are making your DNS records, no-one but you, locally is going to know anything about it.

Yes, I know. I tried pointing a vhost to my sme server and
it would point to the local IP as opposed to the net IP. So
I put it back on the bulkregister dns servers.

my primary site is yevotas.com
IP is 66.72.0.70

I pinged them both at work and the server timed out.
When I pointed the browser to them, I got a site not
found page.

The server is set up as follows:

Ext. Net settings.

Operation Mode server and gateway - dedicated
dhcp client disabled (using static IP address)
static ip address: 66.72.0.70
subnet mask  255.255.255.0
gateway ip address:   blank.


Could my problem be with the gateway ip address being
null?
I can connect to the internet and surf ok as I am posting
this with the above configuration. I am obviousely missing
something simple, right in front of my face and I'm not
seeing it.

A thought just occured to me, do I still need to tell sme
that it is behind a firewall even though it is not behind
the router?

I think I'll change this and see what happens.

Thanks for your help.

Guck Puppy

Re: Virtual Hosts not connecting
« Reply #8 on: August 26, 2003, 02:22:19 AM »
Scott wrote:
> domain is yevotas.com
using the very useful checkdns.net service :
http://www.checkdns.net/quickcheck.aspx?domain=yevotas.com&detailed=1

- Checking http server www.yevotas.com [66.72.0.70]
- HTTP server www.yevotas.com[66.72.0.70] answers on port 80
- Received: HTTP/1.1 200 OK (Server: Apache) . Yevotas Inovations. Yevotas Inovations. . Yevotas home page. hi there, this is a test of the official home server. .

All looks just fine from the net.

when it comes to email though :
- Domain yevotas.com has no MX records, but it has A record for domain. This configuration is NOT recommended

So you might want to specifically add MX records to your domain at your DNS providers control panel.

> The server is set up as follows:
> gateway ip address:   blank.
>
> Could my problem be with the gateway ip address being
> null?
I'm surprised that you can access anything from your SME server without a gateway address. Please do input the gateway there. It will most likely be 66.72.0.1 but your ISP should have provided you with the information.

> A thought just occured to me, do I still need to tell sme
> that it is behind a firewall even though it is not behind
> the router?
Behind a firewall means behind a router. I can't think of a situation where you can have a firewall that is not a router... I guess it could be doing 1:1 NAT or something trippy like that. So, if your SME is not behind a router, it is not behind a firewall.

G

Scott

Re: Virtual Hosts not connecting
« Reply #9 on: August 26, 2003, 02:44:19 AM »
Gary Wrote:

>>http://www.checkdns.net/quickcheck.aspx?domain=yevotas.com&detailed=1

Thanks for the info, this will make checking easier.

>>I'm surprised that you can access anything from your SME server without a >>gateway address. Please do input the gateway there. It will most likely be >>66.72.0.1 but your ISP should have provided you with the information.

I have SBC and they use pppOe which automatically sets this.
It just doesn't show in server-manager.

In the vhost panel, the second column has visibility at
the top. Does this need to be set to Global? You posted
at 17:22 and I changed these setting from Local to
Global at around 17:00. In anycase, the checkdns
site will allow me to experiment a little.
Thanks for the help Gary.

Scott.

Charlie Brady

Re: Virtual Hosts not connecting
« Reply #10 on: August 26, 2003, 02:51:22 AM »
Scott wrote:

> In the vhost panel, the second column has visibility at
> the top. Does this need to be set to Global?

Visibility only has meaning for Mitel ServiceLink customers.

Regards

Charlie

Scott

Re: Virtual Hosts not connecting
« Reply #11 on: August 26, 2003, 03:02:55 AM »
Charlie wrote:

>>Visibility only has meaning for Mitel ServiceLink customers.

Thanks Charlie.

I was doing some checking on the checkdns.net
site and found that while the primary site is
showing ok as Gary posted, the virtual sites
are showing:

  Checking http server www.yevotas.net [66.72.0.70]
  HTTP server www.yevotas.net[66.72.0.70] answers on port 80
  Received: HTTP/1.1 403 Forbidden (Server: Apache) c6 .403 Forbidden.      
  Forbidden. You don't have permission to access / .on this server.. 0 .  
  Server responds with Access Denied.  

So how do I fix this little ditty?

Guck Puppy

Re: Virtual Hosts not connecting
« Reply #12 on: August 27, 2003, 12:06:54 AM »
Scott wrote:

> I have SBC and they use pppOe which automatically sets this.
> It just doesn't show in server-manager.

You use pppOe, ok. pppoe most usually implies you have a dynamic, not static IP address.  I didn't know SBC would allow you to have a static IP address with a pppoe account. Can I ask, how did you convice them to give you a static IP address?

Cheers,

G

Scott

Re: Virtual Hosts not connecting
« Reply #13 on: August 27, 2003, 03:13:05 AM »
Hi G.

Not a problem.
After I had the regular service up
and tested the dynamic for a
couple of weeks, I called SBC
and asked them to upgrade my
account to  the deluxe-s package.

This package gives you 256 Kbps upstream
and 768-1.5 Mbps downstream and 5 static
ip's to go with it for 79.95.
I thought that this was a good starter
package for hosting small websites
like mine.

They also have an
Expert Plus-s package which gives
you 384 Kbps upstream and
1.5 Mbps-6.0Mbps downstream.
and 5 static ips to go with it for
159.95.

Not that your likely to use 5
static ips. But they would
come in real handy if you
decided to put two name
servers online.

Here's something they won't
tell you. For the static package,
you have to set your login to
use static.sbcglobal.whatever
server they give you. Otherwise
you will still have a dynamic ip.

This is something they should have
in there faq page but don't.

Scott.

Scott

Re: Virtual Hosts not connecting
« Reply #14 on: August 27, 2003, 03:14:56 AM »
I figured it out.

The ibays have to be set to internet without
a password. Once this is set, and the
name servers are working right. The
site is up.