[TriLUG] Using Apache 2 with Multiple domains

Mark Fowle mark at thefowles.com
Fri Jul 9 10:09:04 EDT 2004


They would be 2 completely different email servers -  From what I've 
read, I should be able to configure DNS and sendmail to handle both 
domains... just not sure how. Searchs  on google/linux provide lots of 
"theory" stuff - but no examples.....

Turnpike Man wrote:

>Email... kinda depends.  Do you need completely separate instances as if
>running 2 completely different email servers?  OR, like I do at home, I have
>all 3 domains I host separate websites at home all come into one email server,
>postfix.  This means username at example1.com, username at example2.net and
>username at example3.org all go into username's inbox.  I don't have a separate
>inbox for username in each domain per say.  If this is what you want, I can
>help, if you want it as if they were completely separate servers, well, I'd be
>interested to see how postfix gets setup that way, though I don't really need
>it myself.
>
>laters.
>David M.
>
>
>--- "Aaron S. Joyner" <aaron at joyner.ws> wrote:
>  
>
>>Mark Fowle wrote:
>>
>>    
>>
>>>All - I am trying to have multiple domains on a single IP -  I have 
>>>read the apache docs but still am not sure how to set this up.
>>>Does anyone have any good references or how-to's for Apache 2 and 
>>>multiple domains (including the DNS resolutions)?
>>>
>>>What I am trying to do is to have two domains on 1 ip - 
>>>www.thissite.com  and www.anotherone.net  (examples ....) both on 
>>>24.156.43.45
>>>I need to have both be able to have email too....
>>>
>>>I can't seem to understand how to do this based on the docs and an 
>>>older how to I referenced on the web...  Any help would be appreciated!
>>>
>>>Thanks,
>>>Mark
>>>
>>>      
>>>
>># This directive tells Apache to turn on "name based virtual hosting", i.e.
>># directing of requests based on the name the page was requested as
>>NameVirtualHost *:80
>>
>>#
>># VirtualHost example:
>># Almost any Apache directive may go into a VirtualHost container.
>># The first VirtualHost section is used for requests without a known
>># server name.
>>#
>>#<VirtualHost *>
>>#    ServerAdmin webmaster at dummy-host.example.com
>>#    DocumentRoot /www/docs/dummy-host.example.com
>>#    ServerName dummy-host.example.com
>>#    ErrorLog logs/dummy-host.example.com-error_log
>>#    CustomLog logs/dummy-host.example.com-access_log common
>>#</VirtualHost>
>>
>><VirtualHost *:80>
>>    ServerAdmin me at example.com
>>    DocumentRoot /home/thissite/www
>>    ServerName www.thissite.com
>>    ServerAlias thissite.com
>>    ErrorLog logs/thissite-error_log
>>    CustomLog logs/thissite-access_log common
>></VirtualHost>
>>
>><VirtualHost *:80>
>>    ServerAdmin me at example.com
>>    DocumentRoot /home/anotherone/www
>>    ServerName www.anotherone.net
>>    ServerAlias anotherone.net
>>    ErrorLog logs/anotherone-error_log
>>    CustomLog logs/anotherone-access_log common
>></VirtualHost>
>>
>>Email, on the other hand, is a whole different story.  :)  Get Apache 
>>working, then ask again about Email, or check the archives -- both 
>>questions have been answered numerous times before.  :)
>>
>>Aaron J.
>>-- 
>>TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
>>TriLUG Organizational FAQ  : http://trilug.org/faq/
>>TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
>>TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>>
>>    
>>
>
>
>
>		
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail is new and improved - Check it out!
>http://promotions.yahoo.com/new_mail
>  
>



More information about the TriLUG mailing list