[users@httpd] Hosting Scenario

["S. Ural" <su...@fgulen.com>]

There are 2 domains, example.com and example.net seeing the same document
root and thus having the same content.

I want both them get indexed in search engines as separate domains.

 

1-      Do I need to create these 2 domains under Apache separately?

2-      Or aliasing one to another can do the trick?

3-      Does aliasing  mean that only one is Ok to be defined in httpd.conf?
(Pooling the 2nd in DNS will do it work?)

 

 

Thank you

Re: [users@httpd] Hosting Scenario

[so...@apache.org]

On 7/10/08, S. Ural <su...@fgulen.com> wrote:
> There are 2 domains, example.com and example.net seeing the same document
> root and thus having the same content.
> I want both them get indexed in search engines as separate domains.
> 1-      Do I need to create these 2 domains under Apache separately?
> 2-      Or aliasing one to another can do the trick?
> 3-      Does aliasing  mean that only one is Ok to be defined in httpd.conf?
> (Pooling the 2nd in DNS will do it work?)
> Thank you

First, "domains" do not affect Apache httpd.  DNS and Apache httpd can
be completely separate.  DNS defines IP Addresses for server names
within a domain.  Possible server names include the no-name
("example.com"), defined names ("www.example.com" and
"mail.example.com") and the wildcard ("*.example.com") receiving
requests for undefined names.  The Internet sends requests for a named
server to the specified IP Address.  Then the server decides how to
respond.  (Research "ports" and "protocols" for information about
multiple software servers on the same hardware.)

The challenge has always been how to serve different content based on
the server names.  Apache httpd provides this functionality with
"virtual servers."

With no virtual servers, every request to Apache httpd server is
handled alike.  If DNS points multiple server names to the IP Address,
the same content will be served for each of the server names.

The same results happen with virtual servers if the domains are not
defined -- both use the default (first) virtual server and serve the
same content.

The same results happen if multiple server names are aliased in the
virtual server configuration.  The configuration is used for the
specified server names leading to the same content.

The same results happen with virtual servers if the domains use the
same content directory.  The process uses separate configuration
settings to reach the same content.

Unless different virtual servers are configured to use separate
content directories, the same content will be served.  (Rewrite rules
can also serve different content for different server names, but why
bother when virtual servers exist?)
--
Using multiple domains to boost hits is counter-productive.  Traffic
will be split amongst the multiple domains lowering the score for all
the domains.  Better choose a primary domain and use the extra domains
as shortcuts to specific information.  Example:
  http://fgulen.com
can permanently redirect to:
  http://example.com/companies/fgulen/products.html
You can market the short URL while search engines push traffic to the
primary website.

solprovider

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org