From owner-freebsd-questions@FreeBSD.ORG Mon Nov 5 02:50:54 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3594016A41B for ; Mon, 5 Nov 2007 02:50:54 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id 014B013C494 for ; Mon, 5 Nov 2007 02:50:53 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 20502 invoked from network); 4 Nov 2007 20:50:22 -0600 Received: from 124-170-22-248.dyn.iinet.net.au (HELO localhost) (124.170.22.248) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Nov 2007 20:50:21 -0600 Date: Mon, 5 Nov 2007 13:50:17 +1100 From: Norberto Meijome To: Brian Finniff Message-ID: <20071105135017.76a2c48a@meijome.net> In-Reply-To: References: X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: DNS and IP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2007 02:50:54 -0000 On Sun, 4 Nov 2007 18:00:27 -0500 Brian Finniff wrote: > My question is, if you are running a website for 2 different people on the Internet and they both wanted to acquire a domain but you only have one IP address, would it be possible to forward each domain to the same IP address and somehow each one becomes distinct? If so, how is this possible? Can you explain to me how it can be done. > > Oh and for reference, I am not talking about web redirects. Hi Brian, to be more generic in the answer, you can map as many FQDN (fully qualified domain name) as you want to a single IP via DNS (you can even enable wildcard records in certain DNS server software that will match *.yourdomain.com to a default IP). That tells {client_software} that {this_FQDN} is {this_IP}. {client_software}will use that information in whatever form is suitable to {client_software} - in most cases it will contact {server_sofware} running in a server (or group of servers) running as {this_IP}. It is up to {server_software} to determine how the request from {client_software} is handled. For a variety of {server_software}, there is support for named based virtual hosts, where the server will behave differently depending on what FQDN the client is attempting to contact : web servers, FTP servers, etc. Others don't, because it doesn't make sense, or because the protocol used doesn't support such thing (HTTPS, for example). If you want a more specific answer, you need to defined what you want to do. Odds are, you are talking about websites - the other replies to your mail should have answered that point. Best, B _________________________ {Beto|Norberto|Numard} Meijome Q. How do you make God laugh? A. Tell him your plans. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.