Hosting Multiple Web Domains

I have a WRT160N
In the DDNS configuration there is only a space to put one domain name. I have multiple domains hosted off the same web server. Is there a way to add other domains? i.e. comma deliminated or using semi colons, etc
Thanks,
Mike

A work around that works for the most part is to enter a host name in the DDNS section, save it, then replace it with another name and save it. As long as you do not get another dynamic IP....it works.
I guess I will use this work around until I rebuild my Linux router.
Regards
(Mod note: Edited for forum compliance.)

Similar Messages

Hosting multiple web sites usinf personal web sharing

would someone be kind enough to give me a guide to hosting MULTIPLE web sites on a Mac Mini
i have broadband connected to my router
my mac connects to my router with an ip address of 192.168.1.150
I have registered the domain names and want to forward them to the computer hosting the web sites
how can I get each domain name to point to each different web site on my computer

This is a topic you should post to an Apache discussion group being as though Apple's personal web sharing software is Apache.

Single SSL Web Listener for hosting multiple web sites

Hi All,
We are currently hosting multiple websites with Single HTTP Web Listener .. As of now it's everything is working fine..
Now we have planned to have SSL for the hosted sites
Each hosting site will have different SSL Certificates and i am little confused to use Single SSL Web Listener to host multiple web Sites...
Can any one guide me to use Singel SSL Listener for using all hosted sites..
We are having TMG on DMZ Network on Single Nic..
KJSUBBU

Hi,
it is no problem to host multiple SSL websites with only one IP address / certificate on the TMG Server. Only the authentication options for the published websites must be unique, because you cannot use multiple authentication options in one Listener
TMG Server uses HTTPS to HTTPS bridging, so you can use Host header and more to distinguish between the different internal websites:
http://technet.microsoft.com/en-us/library/cc995178.aspx
Regarding the SSL certificate on the internal webservers. TMG must trust the issuing certificate authority which issued certificates for these websites and the name you used to connect from the TMG Server to the internal webserver must part of the CN (Common
Name) or SAN (Subject Alternate Name) on the certificates of the webservers
regards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.galileocomputing.de/3276?GPP=MarcGrote

Hosting multiple web sites.

Dear members:
I am considering OS X Server for a personal project and would like some advice to help me decided what route to take.
My computer will soon be turned into a server hosting my web sites and some other services at my home office. I am thinking about OS X Server as I have done some research and found OS X to require quite a bit of work so that it can do virtual hosting.
How simple is it to configure virtual hosting in OS X Server ? I am considering the latest Leopard version in case it matters. I am not experienced and wish to employ an application that will simplify this process.
Any help will be very appreciated.
Thank you,
Joseph Chamberlain

Joseph:
Although I wouldn't touch any Web-server software other than Mac OS X Server, I should warn you that Apple occasionally favors "pretty" over "practical." I've used PCs and Macs since the Mac Plus was hot, and I've used OS X Server 10.3, 10.4, and now 10.5.3. The last is really excellent, with a gorgeous/powerful Server Admin user-interface, many supporting tools, and thousands of hardball features, but like many Apple "industrial-strength" software products, Mac OS X Server still contains a very few really BAD bugs -- or "oversights" if you prefer.
Before taking the plunge (maybe you already did?), read up on troubleshooting OSX Server's Postfix-based mail service. Even the 10.5.3 upgrade can turn "easy setup" into major frustration; you can do everything by the book and still have weird mail-server glitches. Don't even get me started on documentation for and "centralized" management of Open Directory, Kerberos, etc. I will be migrating to SSL mail security to avoid the user-directory thrash.
When trying to make OSX Server 10.5.3 (a clean install) host *multiple top-level Web domains under a single IP number*, Apple documentation online and on disc didn't offer enough setup detail and virtually NO troubleshooting. Google.com can find what's missing. This archived earlier forum thread saved my bacon....
Topic : "multiple web sites"
http://discussions.apple.com/thread.jspa?threadID=682507
In a nutshell: a multiple-website installation of OSX Server requires careful interaction between the domain-name, IP#, port#, and aliases for each site. When I created my several sites. I relied on the default installation (and Apple instructions) which leaves a wildcard "*" asterisk in each site's Web>Sites>Aliases>WebServerAliases field (in Server Admin). No matter how I diddled with each site's domain-name, IP#, and port# (to create unique combinations), I couldn't force the individual domains to get served independently (despite their shared static IP#) until I DELETED the wildcard WebServerAliases for all the sites. Poof, now it works fine.
Part of the problem is that Apple still publishes documentation on its legendary *drool-proof paper* ("do not expose your LaserWriter to open flame").

Can Snow Leopard host multiple web sites...

I have set up Snow Leopard to host a website by putting my files in the Home/Library/Webserver/Documents to access this site publicly. It works fine. How do I host multiple websites with 1 public IP with out having to use Leopard Server?
Any help is appreciated.

just make a folder in /Library/Webserver/Documents and put all the new stuff there. then add the name of this folder to the website address when entering it in a browser.

Hosting Multiple Mail Domains in SL server on a Mac Mini

So I have been trying to find out the answer to this question, and I keep getting conflicting information, and I am hoping someone here can help me solve this.
We are running two very small business with two different Domains (@company1 & @Company2) Each company has a website, and corporate email. All I want to do is bring all of this in-house onto one Mac Mini server. The calendars and contacts will be shared between the two principle owners of each company (my bosses) as they support each other in there individual business.
The Apple "Genius" says this is not possible, I believe and have been told by a few people and after reading posts on here that it is possible to have multiple domains on one Mac Mini Server. I would like to figure this out quickly as the companies have a need to move off the current email provider as fast as possible due to complications with iOS4 and the iPads.
Any Help from people who are doing this, or know it to be possible or impossible would be greatly appreciated!

This is entirely possible, and supported by the Server Admin user interface for the mail server.
Start with the [Mac OS X Server Mail Services Administration Manual|http://images.apple.com/server/macosx/docs/MailService_Adminv10.6.pdf], page 73
Quoth the Book Of Mail:
A Mail Service Virtual Host
Virtual hosting is a method you can use to host more than one domain name on the same
computer and IP address, with overlapping mail user names.
For example, a mail server can receive mail transfer requests for two domains,
mail.example1.com and mail.example2.com, both of which resolve to the same IP
address. For mail.example1.com, the server delivers mail to “[email protected]”
to a user mailbox for “bob,” while it also delivers mail to “[email protected]” to
a different user mailbox. Virtual hosts are essentially the converse of local host aliases.
One subtlety here is that the domains sharing the same mail server and all co-resident on the IP address will all tend to have the same public host name listed as their MX (mail exchange) server of record in the public DNS. This so that forward and reverse DNS and MX server all line up for the mail server for all the domains involved.

Hosting Multiple Mail Domains

Hi There:
I have some questions, will you please help me.
My Server is set
example.com
I need to set additional / Multiple E-Mail Domains, these need to be separated, like:
example1.com
example2.com
example3.com
For the E-Mail Client, what will be de In-Comming Mail Server and Out-Going / SMTP
mail.example1.com
mail.example2.com
mail.example3.com
or it will be "mail.example.com" for all 4 Domains.
I would like to say THANK YOU in advance

This is entirely possible, and supported by the Server Admin user interface for the mail server.
Start with the [Mac OS X Server Mail Services Administration Manual|http://images.apple.com/server/macosx/docs/MailService_Adminv10.6.pdf], page 73
Quoth the Book Of Mail:
A Mail Service Virtual Host
Virtual hosting is a method you can use to host more than one domain name on the same
computer and IP address, with overlapping mail user names.
For example, a mail server can receive mail transfer requests for two domains,
mail.example1.com and mail.example2.com, both of which resolve to the same IP
address. For mail.example1.com, the server delivers mail to “[email protected]”
to a user mailbox for “bob,” while it also delivers mail to “[email protected]” to
a different user mailbox. Virtual hosts are essentially the converse of local host aliases.
One subtlety here is that the domains sharing the same mail server and all co-resident on the IP address will all tend to have the same public host name listed as their MX (mail exchange) server of record in the public DNS. This so that forward and reverse DNS and MX server all line up for the mail server for all the domains involved.

ACE probing of "virtual hosts" on web servers

We got some web servers that hosts multiple web sites and would like to probe each of these sites. Is there a way to configure a probe to present the request for a particular web site versus the other without falling into the catch all clause of the http server configured on the box ?
Thanks

Hello Folks,
I wonder if you could get away with just using the built-in HTTP probe rather than the scripted probe? With the built-in HTTP probe, you can configure all sorts of HTTP headers, including the Host header which might be all you need for your server hosting multiple sites.
Just to clarify on the support for scripted probes that TAC supports: If the script is downloaded from cisco.com, and is not modified, then TAC will support it. It is not supported if it is modified, and TAC will not support custom-created scripts.
Hope this helps,
Sean

Hosting mutiple web sites

How do I host multiple web sites in OS 10.4 server? I know how to do virtual web sites by editing the httpd.conf. I want to know how to do that in the GUI.

Have you looked at Server Admin?
It's pretty straightforward - connect to the server, select Web and hit the Sites tab. Add as many sites as you like, using either different ports or different hostnames for each one.
It will create a separate .conf file for each virtual host.

How do I host multiple domains on a single Messaging Server?

How do I host multiple domains on a single Messaging Server?
<p>
To host multiple domains on one Messaging Server, use the
mailAlternateAddress attribute. If you want to host two domains
(customer1.com and customer2.com) on your server mail1.domain.com,
make sure that:
The various domains (in DNS) point to the installed mail server
(you must have the MX records that
points mail for customer1.com to mail1.domain.com and
customer2.com to mail1.domain.com)
That each person receiving mail at customer1.com and
customer2.com has an appropriate mailAlternateAddress
attribute describing the appropriate email address. For
instance, John Doe can have an email address (i.e. the value
of the 'mail' attribute for the John Doe LDAP entry) of
[email protected] and receive his mail on
[email protected] (the value of the mailAlternateAddress
attribute)
With Messaging Server 3.5, mailAlternateAddress can take the
form of @mail1.domain.com. If jdoe's mailAlternateAddress is
set to @mail1.domain.com, mail sent to [email protected]
will be delivered to [email protected]

jaygatsby1123 wrote:
So what exactly am I doing with virtual hosts? There is a place for Aliases... What would I put in the "Aliases" box?
Any other host name that you want to resolve to the specified virtual host. It's quite literally an alias.
if you want www.example.com and www.example.org to end up at the same web site and you already have a virtual host — Apple refers to virtual hosts as sites — configured for www.example.com in Server.app, then you'd add www.example.org as an alias for the www.example.com virtual host (site).
Virtual hosts are implemented in a web server using some details of the HTTP or HTTPS protocol, and what the web browser (client) specified. The client gets handed an IP address or a domain name by the user, and the client then fetches the associated IP address for the target web server from the client's DNS services or local host database, and the client then connects to the IP address and passes over the text string that the user had requested — the IP address or domain name or even some local shortcut set up in the client system — via the HTTP or HTTPS protocol. The web server receives and processes this arriving text string from the client, and uses it to select which web site to render back to the web client. One subtle detail lurks here, too: the server's own DNS configuration really isn't involved in the selection of the virtual host.

Can you host multiple domain names on mobile me with iWeb '09?

Hi
Can anyone help, before I upgrade to iLife '09, I have a personal web domain name which I host on my mobileme account. My girlfriend now wants a website and I have bought her a domain name and want to use iWeb to design it but I can't seem to host multiple domains on iWeb '08, can you with iLife '09? Or will she have to buy her own mobile me account? Any help will be great!!!
Thanks

MobileMe -MME -is Apple's hosting service.
Domain Name System - DNS translates an understandable address like www.mywebsite.com into the IP address which is a number like 40:75:92:301.
Cname is a name of record in a database that records what domain name goes to what IP address.
IP address is just a unique number that identifies any device connected to the internet.
An FTP client is an application the uploads your files to a server using File Transfer Protocol.
I mainly use Web Site Maestro because it doesn't just upload the files but optimizes them first to remove all the unnecessary code that iWeb creates to allow your website to download at least 30% faster.
I also use Yummy FTP for sorting out and keeping track of my files on the server and uploading folders of images and music files along with their assets for flash presentations.
I have used Host Excellence for years because of the way they allow you to name your own root folder on the server and also their great tech support.
FTP and servers can be a bit confusing but, if you have a good hosting company, you can get by on very little knowledge and understanding. I do!
I couldn't agree more with you about the acronyms and jargon. The more people use them usually means the less they know. One of the most misused words is "domain". I tried to sort that one out here...
http://www.iwebformusicians.com/SearchEngines/Upload.html
Now I'm going FUH and ATNP.

Setting up multiple web sites (virtual hosting).

Dear members:
I am considering OS X Server for a personal project and would like some advice to help me decided what route to take.
My computer will soon be turned into a server hosting my web sites and some other services at my home office. I am thinking about OS X Server as I have done some research and found OS X to require quite a bit of work so that it can do virtual hosting.
How simple is it to configure virtual hosting in OS X Server ? I am considering the latest Leopard version in case it matters. I am not experienced and wish to employ an application that will simplify this process.
Any help will be very appreciated.
Thank you,
Joseph Chamberlain

You could create local PAC file <http://findproxyforurl.com/pac_file_examples.html> where you can return multiple PROXY servers. You would create text file with your PAC script in it. Then specify System Preferences -> Network -> Advanced -> Proxy -> Automatic Proxy Configuration, and click "Choose File".
If you choose to take BDAqua's advice and create multiple Network Locations, you can then use either
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy1"
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy2"
/usr/sbin/networksetup -switchtolocation "MyCompanysProxy3"
or
/usr/sbin/scselect "MyCompanysProxy1"
/usr/sbin/scselect "MyCompanysProxy2"
/usr/sbin/scselect "MyCompanysProxy3"
you can put them into a script of your choosing. Shell script, or Automator Run Shell Scirpt, or Applescirpt do shell script (or Perl, Python, Ruby, etc...)

Lync 2013 certificate requirements for multiple SIP domains

Hi All,
I am engaged with a client in respect of a Lync 2013 implementation initially as a conferencing platform with a view to enabling EV functions (inc. PSTN conferencing) in the future. They initially need to support 30 SIP domains and eventually
around 100 SIP domains which is proving to be either not possible or severely cost prohibitive. Their current certificate provider, Thawte, can only support up to 25 SANs and have quoted them 5 figures. We tend to use GeoTrust as they are cheaper but they
appear to have a limit of 25 SANs. GoDaddy appear to support up to 100 SANs for a pretty reasonable cost. My questions are as follows:
Is there a way that I’m missing of reducing the number of SANs required on the Edge server?
Use aliases for access edge FQDNs - Supported by desktop client but not by other devices so not really workable
Don’t support XMPP federation therefore removing the need for domain name FQDNs for each SIP domain
Is there a way that I’m missing of reducing the number of SANs required on the Reverse Proxy server?
Friendly URL option 3 from this page:
http://technet.microsoft.com/en-us/library/gg398287.aspx
Client auto-configuration:
i.
Don’t support mobile client auto-configuration in which case no lyncdiscover.sipdomain1.com DNS records or SANs would be required.
ii.
Support mobile client auto-configuration over HTTP only in which case CNAME records are required for each SIP domain (lyncdiscover.sipdomain1.com, etc. pointing to lyncdiscover.designateddomain.com) but no SANs are required.
iii.
Support mobile client auto-configuration over HTTPS in which case DNS records are required for each SIP domain and a SAN entry for each SIP domains is also required. This is because a DNS CNAME to another domain is not supported over
HTTPS.
If the answer to 1 and/or 2 is no, are there certificate providers that support over 100 SANs?
How do certificate requirements differ when using the Lync 2013 hosting pack? I would think that this issue is something that a hosting provider would need to overcome.
Would the Lync 2013 Hosting Pack work for this customer? The customer uses SPLA licensing so I think is eligible to use the hosting pack but not 100% sure it will work in their environment given that client connections are supposed
to all come through the Edge where their tenants will be internal and also given the requirement for an ACP for PSTN conferencing.
Many thanks,

Many thanks for the response.
I was already planning to use option 3 from the below page for simple URLs to cut down on SAN requirement.
http://technet.microsoft.com/en-us/library/gg398287.aspx
What are the security concerns for publishing autodiscover over port 80? I.e. Is this only used for the initial download of the discovery record and then HTTPS is used for authentication? This seems to be the case from the following note on the below page:
http://technet.microsoft.com/en-gb/library/hh690030.aspx
Mobile device clients do not support multiple Secure Sockets Layer (SSL) certificates from different domains. Therefore, CNAME redirection to different domains is not supported over HTTPS. For example, a DNS CNAME record for lyncdiscover.contoso.com that redirects
to an address of director.contoso.net is not supported over HTTPS.
In such a topology, a mobile device client needs to use HTTP for the first request, so that the CNAME redirection is resolved over HTTP. Subsequent requests then use HTTPS. To support this scenario, you need to configure your reverse proxy with a web publishing
rule for port 80 (HTTP).
For details, see "To create a web publishing rule for port 80" in Configuring the Reverse Proxy for Mobility. CNAME redirection to the same domain is supported over HTTPS. In this case, the destination domain's certificate covers the originating
domain.”
I don’t think SRV records for additional SIP domain access edge is a workable solution as this is not supported by some devices.
As per the below article:
http://blog.schertz.name/2012/07/lync-edge-server-best-practices/
“The recommended approach for external client Automatic Sign-In when supporting multiple SIP domains is to include a unique Access Edge FQDN for each domain name in the SAN field. This is no longer a requirement (it was in OCS) as it is possible to
create a DNS Service Locator Record (SRV) for each additional SIP domain yet have them all point back to the same original FQDN for the Access Edge service (e.g. sip.mslync.net).
This approach will trigger a security alert in Windows Lync clients which can be accepted by the user, but some other clients and devices are unable to connect when the Automatic Sign-In process returns a pair of SRV and Host (A) records which do not share
the same domain namespace. Thus it is still best practice to define a unique FQDN for each additional SIP domain and include that hostname in the external Edge certificate’s SAN field”.
===================
1. Basically the requirement is to initially provide Lync conferencing services (minus PSTN conferencing) to internal, external, federated and anonymous participants with a view to providing PSTN conferencing and therefore enterprise voice services later.
2. The customer currently supports close to 100 SMTP domains and wants to align their SIP domains with these existing domains. The structure of their business is such that “XXX IT Services” provide the IT infrastructure for a collection of companies who
fall under the XXX umbrella but are very much run as individual entities.
Question:
Would you agree that I’m going to need a SAN for every SIP domain’s access edge FQDN?
Thanks.

Lab setup multiple SIP domains for federation

I have been setting up multiple Lync 2013 lab environments and have a question about my external DNS environment. I have installed server 2012R2 on the host running the lab with its own domain (contoso.local). I have this server which hosts a separate domain,
Hyper-V and a CA, this is what I am using for my external environment. The network IP is 10.0.0.0/16.
I set up a server called vRouter that has 3 NICs. In Hyper-v I have 3 virtual switches configured. One for the External environment - 10.0.0.0/16 (not necessary for lab, setup to transfer needed files from internet to VMs), one for 192.168.1.0/24, and one
with 192.168.2.0/24. The virtual router has RRAS installed and can route traffic between 192.168.1.0/24 and 192.168.2.0/24.
My VMs for the lab are as follows.
1test.local
AD1.1test.local -192.168.1.100
FE1.1test.local - 192.168.1.200
Edge1 - 192.168.1.210int, 10.0.5.10ext
2test.local
AD2.1test.local -192.168.1.100
FE2.1test.local - 192.168.1.200
Edge2.1test.local - 192.168.1.210int, 10.0.6.10ext
Both environments have users that can log into lync and message each other.
When installing the Edge servers I used the same FQDN and IP for the external interface since all ports are open and firewalls have been disabled internally. I installed the internal certificate from the AD server which has CA role in each environment. On
the external device I used the Host's CA to get certificates for both Edge servers. The Edge servers have 2 NICs one on their expected internal environment with no Gateway. And one on the external environment. These servers are not part of any domain. however
I did add the contoso.local to the primary DNS suffix when domain membership changes under system properties. I then created the two following A records on the host computer (10.0.0.0\16 network, contoso.local) to be able to see router their external traffic.
Edge1.contoso.local 10.0.5.10
Edge2.contoso.local 10.0.6.10
Both of these FQDNs are what is in my topology for the Access Edge service, Web Conferencing Edge Service, and A/v Edge Service with the same IP using different ports in both environments.
Both environments are set up to support the other SIP domain. However when I try to add a user from the other domain I cannot communicate with that user nor see their presence.
I looked over my external DNS settings and realized that I had not set a SRV record on the 10.0.0.0\16 network(external).
I then realized that if I try to add the traditional _sipfederationtls._tcp.contoso.local I will have 2 conflicting entries.
One for:
_sipfederationtls._tcp.contoso.local - 10.0.5.10 (1test.local edge)
and one for:
_sipfederationtls._tcp.contoso.local - 10.0.6.10 (2test.local edge)
Should I spin up another VM and make that a DC with a CA and trust it to the host computer, set up conditional forwarders. Something like Trust.local and correct the DNS, topology builder FQDN, and certificates on the second edge server?
Edge2.trust.local
Or can I add a new zone to my host computer then correct the DNS, topology builder FQDN, Certificates?
Or am I missing another external DNS record on my contoso.local environment?
Can I set up a CNAME entry that will mask the second edge server?
Any input would be appreciated.
Thanks

If contoso.com is not a sip domain, then you won't need that DNS record at all. Those records are autodiscover records that Lync uses based upon the sip domain.
So you'd need
_sipfederationtls._tcp.1test.local
and
_sipfederationtls._tcp.2test.local
What effectively happens, is when someone on the outside tries to IM
[email protected], their Lync edge server will see the 1test.local and query the appropriate above record for it so it knows where to communicate.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Multiple Web Sites on OS X Mavericks Server

I want to run multiple test web sites off my home Mac OS X Mavericks Server 10.9 can someone point me to a good "How to" on the specific of how to use the Server application to create and operate multiple web sites of a single Mavericks Server?
Example
MyServer.inno.com          10.0.2.5
Basic web is up and running....
I want to host four other web sites off the same machine for testing purposes how do I do that?
MyServer.inno.com          10.0.2.5
MyServer.web1.com          10.0.2.5
MyServer.web2.com          10.0.2.5
MyServer.web3.com          10.0.2.5
MyServer.web4.com          10.0.2.5
so if I go to the server and load
     MyServer.web1.com          10.0.2.5
it load a different web server.
My thought is to use virtual host how does Apple / Community recommend I set this up...
T.

Please do not squat in the "home.com" domain. If you're going to use a bogus domain, please use a bogus to-level domain such as server.home.jarvis — .jarvis is not currently a valid top-level domain, though that might change with the way ICANN has been bringing many new top-levels online, so a real registration is safer here.
Peter Jarvis wrote:
Assumptions:
     1. The Server is not intended to be publicly accessable from the Internet
How will it be accessed? Entirely privately? No external access? OK.
     2. Private Network - 10.0.1.X
I'd probably pick something a little further into 10, such as 10.8 or 10.10, or 10.20.1.x — if you're ever using a VPN, it's best to use a weirder subnet, and I've worked with several folks that have 10.0.1.0/24 subnets.
     3. DHCP Reservation for the Mac Server - 10.0.1.2.
I usually prefer keep the server and the other fixed-address hosts outside the DHCP pool.
     4. Server Domain name MacServer.home.com
Are you the registrant for the home.com domain? (I'd tend to doubt that, and would therefore suggest use of a real and registered domain or subdomain that you have permission to use or (less desirably) use a bogus top-level domain.)
     5. Example Web Site http:www.rouxacademy.com to also run off the same server...
Is that going to be public?
Prequisites:
     1. Static Server IP Address / DHCP Reserved IP Address against MAC Address
     2. DNS Service Configured and Running
     3. Web Service Configured and Running
     4. Example Web Site http:www.rouxacademy.com
     5. You have a basic website (with mysql) files available
               Directory roux_academy (Contains Basic Web SIte files etc)
OK.
Steps:
     1. Static Server IP Address / DHCP Reserved IP Address against MAC Address
The Airport Airport allows you to Reserve and IP address against a MAC (Media Access Control) physicall address of Server Ethernet Card. You can do this or have the Airport allocated DHCP address from 10.0.1.50 and above and statically allocate the server address of the machine.
I'd leave the server out of the address pool. So long as the pool and all static IP hosts are in the same block (usually a 255.255.255.0 or /24 subnet) it'll all work, and you won't need to entangle the OS X Server with the DHCP server.
     2. DNS Service Configured and Running
Install Mavricks, install OS X Server application, launch server app...
Go to DNS tab, define a new host name MacServer.home.com and associate with 10.0.1.2 IP Addresss
Start DNS Service...
Note: DO not publish DNS service via airport to Internet...
Other than not squatting in that domain, yes. There's no reason to open TCP or UDP port 53 inbound.
   3. Web Service Configured and Running
Go to Web Sites tab...
Click + and create new web site entry
Domain Name:                http:www.rouxacademy.com
IP Address:                     Any
SSL:                               None
Store Files in:                /Volumes/dev/Library/Server/Web/Data/Sites/roux_academy
Who can access:          Anyone # I would restrict to a single user
Additional Domains:     rouxacademy.com
no http: prefix there, but yes.
If you're not exposing the server to the 'net (as mentioned above) there's probably no need to restrict. If you do need to restrict, you'll need to edit configuration files for Apache, or some other technique — maybe a VPN, if you're allowing (controlled, VPN-based) inbound access into your network.
Start Web Service...
     4. Back to DNS
Add host name....
www.rouxacademy.com / 10.0.1.2
# Do not create an MX record or publish DNS via airport...
AirPort does not know from MX records, and does not provide DNS services. AirPort will know about your local DNS server, since you are apparently using the AirPort for DHCP.
You can also add the DNS translation during step 2; Apache and DNS are not tightly linked here.
Launch Safari and type
     www.rouxacademy.com          - should launch web site...
     rouxacademy.com                   - should launch web site
Caveat: the Real rouxacademy.com will not be accesable from the server or local machines on 10.0.1.X network...
Ah, so there's a key detail — you're playing games and mimicking a real web site? OK.
The rouxacademy.com web site will be accessible from the server, as that'll (also) have the DNS translation (and remember the basis for virtual hosting is the client — the server in this case — has a translation for the host — the rouxacademy.com or www.rouxacademy.com domain in this case — and passes that string over the HTTP or HTTPS connection to the web server.   If you really want to keep the server from accessing this web site, then you'll have to push the local translation of that domain into the hosts file, or to a separate DNS server.
I'd try to avoid this configuration though, particularly as your references to MX earlier implies that this domain might be more active than just the web services discussed here — trying to run split-horizon DNS means you'll get what's internal and external somewhat tangled, and you'll have to keep mail — for instance — aimed outside and web services aimed internally. This is possible for many cases, but gets tricky.
Best to test the web site with a different domain name, and to use /-relative notation for accessing the files, or using the web content management system's configuration settings to control the "published" name of the site.

Hosting Multiple Web Domains

Similar Messages

Maybe you are looking for