Re: url forward

2000-11-19 Thread Sebastiaan
Thanks! That's a start , because the page is not locally hosted.

Greetings,
Sebastiaan.

On Sat, 18 Nov 2000, Martin Würtele wrote:

 On Sat, Nov 18, 2000 at 05:55:20PM +0100, Sebastiaan wrote:
  Ok, does anyone know an elegant (and fast) method to accomplish this, so
  that the original domain name (www.dorpsnet.nl) stays in the url (so that
  www.dorpsnet.nl is equivalent to 194.235.126.184/~sebas)?
  
 set the ip for www.dorpsnet.nl to 194.235.126.184 and in apache use
 virtualhosts:
 
 --begin--
 
 NameVirtualHost 194.235.126.184
 
 VirtualHost 194.235.126.184
 ServerName www.dorpsnet.nl
 # ad this line if you want access without www as well:
 ServerAlias dorpsnet.nl   
 # tell apache where the files ar:
 DocumentRoot /home/sebas/public_html 
 # log files:
 ErrorLog /var/log/apache/dorpsnet_error.log
 TransLog /var/log/apache/sorpsnet_access.log
 
 # open index.html and index.htm automatically
 DirectoryIndex index.html index.htm
 /VirtualHost
 
 --end--
 
 this should do the job.
 
 hth martin
 



Re: url forward

2000-11-19 Thread Sebastiaan
Thanks,
I will discuss this with my provider when really needed.

Greetings,
Sebastiaan
 
 You can't do this with DNS alone; your provider needs to run a virtual
 host for you. Whenever any HTTP/1.1 client (or HTTP/1.0 client with
 Netscape extensions, the two of which combined form the vast majority of
 even vaguely recent browsers) sends a request for one of your pages, it
 sends the HTTP header Host: www.dorpsnet.nl. Your provider's web
 server then needs to recognize that and send them back pages from the
 directory ~sebas.
 
 This should be trivial for a provider who knows anything at all about
 web hosting.
 
 -- 
 Colin Watson [EMAIL PROTECTED]
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null
 
 



url forward

2000-11-18 Thread Sebastiaan
Hello,

I am new to domain name servers, so I may ask stupid questions, but I hope
someone can help me. I have just set up a nameserver which works fine. 
Now I want to forward my www to my internet provider, but there is a
slight problem. My page does not have an ip, but is in fact a directory on
the server of my provider. This is my situation:

/etc/bind/db.dorpsnet contains the lines:
local   A   192.168.1.254
www A   194.235.126.184

so when I acces www.dorpsnet.nl (local name) I succesfully reach the
provider's home page. But unfortunately, my homepage is at
194.235.126.184/~sebas

Can you give me a hint or some tips how to manage this? Can this be done
with DNS, or do I have to install another package?

Thanks in advance,
Sebastiaan





Re: url forward

2000-11-18 Thread Ethan Benson
On Sat, Nov 18, 2000 at 04:50:10PM +0100, Sebastiaan wrote:
 Hello,
 
 I am new to domain name servers, so I may ask stupid questions, but I hope
 someone can help me. I have just set up a nameserver which works fine. 
 Now I want to forward my www to my internet provider, but there is a
 slight problem. My page does not have an ip, but is in fact a directory on
 the server of my provider. This is my situation:
 
 /etc/bind/db.dorpsnet contains the lines:
 local A   192.168.1.254
 www   A   194.235.126.184
 
 so when I acces www.dorpsnet.nl (local name) I succesfully reach the
 provider's home page. But unfortunately, my homepage is at
 194.235.126.184/~sebas
 
 Can you give me a hint or some tips how to manage this? Can this be done
 with DNS, or do I have to install another package?

no, DNS is only responsible for translating domain names into IP
addresses, it knows nothing about web server directories, or even
about web servers period.  

i think what you would do is run apache or some small httpd that
simply redirects to http://194.235.126.184/~sebas

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpLXQsPZAJvD.pgp
Description: PGP signature


Re: url forward

2000-11-18 Thread Sebastiaan
Ok, does anyone know an elegant (and fast) method to accomplish this, so
that the original domain name (www.dorpsnet.nl) stays in the url (so that
www.dorpsnet.nl is equivalent to 194.235.126.184/~sebas)?

Thanks in advance,
Sebastiaan


On Sat, 18 Nov 2000, Ethan Benson wrote:

 On Sat, Nov 18, 2000 at 04:50:10PM +0100, Sebastiaan wrote:
  Hello,
  
  I am new to domain name servers, so I may ask stupid questions, but I hope
  someone can help me. I have just set up a nameserver which works fine. 
  Now I want to forward my www to my internet provider, but there is a
  slight problem. My page does not have an ip, but is in fact a directory on
  the server of my provider.

 no, DNS is only responsible for translating domain names into IP
 addresses, it knows nothing about web server directories, or even
 about web servers period.  
 
 i think what you would do is run apache or some small httpd that
 simply redirects to http://194.235.126.184/~sebas
 
 -- 
 Ethan Benson
 http://www.alaska.net/~erbenson/
 



Re: url forward

2000-11-18 Thread Colin Watson
Sebastiaan [EMAIL PROTECTED] wrote:
I am new to domain name servers, so I may ask stupid questions, but I hope
someone can help me. I have just set up a nameserver which works fine. 
Now I want to forward my www to my internet provider, but there is a
slight problem. My page does not have an ip, but is in fact a directory on
the server of my provider. This is my situation:

/etc/bind/db.dorpsnet contains the lines:
local  A   192.168.1.254
wwwA   194.235.126.184

so when I acces www.dorpsnet.nl (local name) I succesfully reach the
provider's home page. But unfortunately, my homepage is at
194.235.126.184/~sebas

Can you give me a hint or some tips how to manage this? Can this be done
with DNS, or do I have to install another package?

You can't do this with DNS alone; your provider needs to run a virtual
host for you. Whenever any HTTP/1.1 client (or HTTP/1.0 client with
Netscape extensions, the two of which combined form the vast majority of
even vaguely recent browsers) sends a request for one of your pages, it
sends the HTTP header Host: www.dorpsnet.nl. Your provider's web
server then needs to recognize that and send them back pages from the
directory ~sebas.

This should be trivial for a provider who knows anything at all about
web hosting.

-- 
Colin Watson [EMAIL PROTECTED]