Koozali.org: home of the SME Server

website not accessible

aniston

website not accessible
« on: March 10, 2001, 08:31:34 PM »
I posted this on the experienced user forum but got no response ...maybe it is a silly little problem....if anyone has any ideas please help out, thanks.

hello,

I have the esmith v 4.1 running up and well with a static ip thru my adsl provider in italy. I have set the domain name as berzek.org and internally it works well if i do a www.berzek.org i can see my web site.

I have a registered domain name with easyspace.com and the my domain berzek.org has its name server pointing to ADSL-213-38.19-151.NET24.IT which even calculates its real ip address of 151.38.19.213 my fixed ip address from my adsl service provider.

but doing a www.berzek.org from outside my lan (eg simple modem only connected PC) i dont get any response. Even a ping to www.berzek.org does not gice me a response not even a request timed out response. Someone mentioned about a reverse lookup zone that may need to be configured but have no idea where and how to do that.

Any ideas ?

one thing to note i set up a dyndns account to get by my non working web site and that works try looking at www.ccare.dyn.dns.org and you will see the simple neat e-smith web page. So I'm quite sure that the apache web server is responding to external querries on port 80. But i dont know why an external ping to www.berzek.org not respond.

Finally i did a whois database lookup and even that works well as it shows my real static internet ip correctly as 151.38.19.213 so surely i have to set this thing of reverse lookup zone somewhere as the ping does not even reply with the famous "timed out" response when it cannot find the address.

If this post is in the wrong place.... please foward it to the right one.

thanks to all at esmith in advance on the lovely simple server distribution.

cheers once again.
aniston.

Charlie Brady

Re: website not accessible
« Reply #1 on: March 10, 2001, 08:51:24 PM »
aniston wrote:

> I have a registered domain name with easyspace.com and the my
> domain berzek.org has its name server pointing to
> ADSL-213-38.19-151.NET24.IT which even calculates its real ip
> address of 151.38.19.213 my fixed ip address from my adsl
> service provider.

The e-smith server does not host a publicly visible name server, so you should not point any name server records at it. You need to have your full domain DNS hosted elsewhere.

Charlie

aniston

Re: website not accessible
« Reply #2 on: March 10, 2001, 09:13:22 PM »
thanks charlie ...so are there any publically free dns hosting services to resolve that?...

an idea crops up would inserting the dns address in the admin terminal config help in resolving the problem ?

chrres
aniston.

PS: We have nearly completed our translations of e-smith in italian for the webmanager pages...only problem is inserting these characters in the perl scripts eg: òçàùèé' and °    ....if theres a way to insert those characters in the perl scripts please let us know the way as of now we tried avaiding most words that had those characters.

Paul Miller

Re: website not accessible
« Reply #3 on: March 14, 2001, 08:45:48 PM »
aniston wrote:
>
> thanks charlie ...so are there any publically free dns
> hosting services to resolve that?...

Hammernode at hn.org provides free primary name service.

See this post from Paul Chubb for how to integrate into e-smith.

http://forums.contribs.org/index.php?topic=10338.msg38963#msg38963

You will need to use your registration service (Internic or other)  to point the hn.org nameservers to your domain.  This will take a few days.  I am in the process of moving my domain to them.

Let me know if you need help.

Good luck,
Paul Miller

JeromeV

Re: website not accessible
« Reply #4 on: March 16, 2001, 06:03:28 PM »
Bonjour
J'utilise e-smith sur une connexion adsl avec ip fixe.
J'ai également un domaine enregistré chez gandi et j'utilise les services de dns de hammernode. Si j'ai bien tout compris, j'imagine que je dois répliqué manuellement chez hammernode tous les records indiquiés dans e-smith (mail, www, ftp ainsi que les domaines virtuels).
Est ce une charge trop lourde pour e-smith de gérer lui meme son dns primaire ?