DNS zones for Mail virtual host

Hello,
We have a split DNS server hosting mail for company.com. So we have a DNS zone called company.com with the appropriate records (A, MX).
We now need in the same box to host mail for another domain, company.org. Do we have to create a separate DNS zone for company.org with another A record for the server?
Regards
Kostas

If you're going strictly for mail and with no other network services are associated, then Camelot is quite correct and you can use an MX, and enable virtual hosting within the mail server.
If you're doing "other stuff" with that domain, then you'll need the zone.
Given the usual fondness for, well, "incomplete" questions and for server configurations and networks that, um, "evolve", then the answer I'd use is "yes"; add the zone. (If for no other reason than somebody's eventually going to want a web server with the domain, or...)
I'm not a big fan of split-horizon though I can and do use it for specific cases. I prefer to partition "inside" from "outside", and that avoids this quagmire.
And FWIW, "example.com", "example.org" and "example.net" are RFC-reserved domain names available for posting obfuscated examples and questions, for documentation, and related use. "company.com" and "company.org" are real and registered domains.

Similar Messages

DNS Zone for Mail

Following on from my first question which the nice Mr Camelot answered for me
I have a server which has a DNS zone of companyname.net.
Internal mail has been setup using Mail Exchanger set to mail.companyname.net.
I have checked changeip -checkhostname and there are no issues.
The public DNS records have been set to make mail.companyname.com the MX record, and an A record for mail.companyname.com has been setup pointing to the static IP.
As I see it I have two options I can move forward with (3 actually if I wipe the server and start again )
1. Try and rename the DNS zone to companyname.com and then reset the mail settings to match.
2. Setup a CNAME on the server internal DNS to point mail.companyname.com to mail.companyname.net and leave the mail settings as they are.
I am in the process of installing SL Server on a VM to test the first option to see if it is viable, but my question is are there any options I have missed, and what would you suggest I do in this circumstance?
TIA.

So you have a zone for a host mail.example.net within your network, and valid external DNS services with an A record and MX at mail.example.com within your external DNS services, and you're wondering about rebuilding this all?
It'd be far easier to just enable mail.companyname.com as a virtual host within the mail server configuration.
Personally, I'd look to remove the use of the internal example.net MX for the mail server, and use the external path. You can set up the MX for the internal network to resolve to mail.example.com, for instance. With that (and with a firewall that knows how to reflect" outbound traffic for the WAN IP address, or - somewhat uglier - adding a DNS A record for the mail.example.com within your internal zone), the configuration is the same for all hosts, whether internal desktops or mobile devices.
Note that the companyname.com and companyname.net domains are real and registered domains. The domains example.com, example.net and example.org are RFC-reserved for documentation and for these sorts of postings.

Correct DNS Setup for Mailman Virtual Host?

DNS gurus, help please: I'm setting up a new Snow Leopard server that will rely upon an external name server. The single PTR record for this server will be the server's primary website, www.ourprimarydomain.topleveldomain . This primary domain name currently resolves to our current production server. I'm migrating Mailman before the primary website, and I'd like for Mailman to use a subdomain like mailinglists.ourprimarydomain.topleveldomain . This subdomain currently resolves to Mailman on our current production server. For testing before we switch to the new server, I'd like to set up a sub-subdomain development.mailinglists.ourprimarydomain.topleveldomain .
Clear as mud? Here's what I think that I need in our external DNS, is this the best way?
A: development.mailinglists.ourprimarydomain.topleveldomain -> new server IP
MX: development.mailinglists.ourprimarydomain.topleveldomain -> new server IP
PTR: none until we migrate primary website
Will this break anything? If we need a PTR record, perhaps we should register an external domain name that isn't our primary website.
What about C records? Should I register aliases?
Thanks for your advice,
Ted

OK, I've changed my plan. I think that this is the best for my scenario:
Register an external A, MX, and PTR for development.mailinglists.ourprimarydomain.topleveldomain -- I read that some email spam filtering systems use PTR (reverse lookup) as one factor in spam identification. So I want a PTR to begin with for testing. Once the mailing lists are migrated, I simply request that the current production domains point to the new IP.
So ... I think that's it

Oracle Portal Virtual Host Enhacement for Multiple Virtual Hosts

I open the TAR Number: 4326752.996
The TAR is related to " REQUEST ASSISTANCE FOR MULTIPLE VIRTUAL HOSTS AND MULTIPLE PAGE GROUPS CONFIG. "
This is the Scenario: We Have Oracle Portal installed in a single Box. yes I know I know... but Not everybody is Yahoo or Google for Clusters and all the good stuff, we just want our website managed by Oracle Portal since all our ERP is running Oracle Database. Anyway. 1 Box running Oracle Portal Infrastructure and MidTier.
It turns out that our previous configuration we have the LAMP Solution with PHP, Apache with Virtual Servers configuration very trivial for a regular web server however we have about 6 Virtual domains.
For example:
www.abc.com
www.def.com
www.ghi.com
www.jkl.com
www.mno.com
www.pqr.com
We also like to post all our Intranet Information in this great Portal:
http://intranet.com
Where intranet.com is the same server but setup in our Internal DNS without be a Real Internet Register Domain.
So bottom line we start doing great with Install our single box install, later [GRRRRRR does not come by default in port 80 GRRRRRR, ok need to move and setup the virtual host to resolve our main External website www.abc.com ]
For starters ok it worked we have our main website running Oracle Portal.
Now is time to go to the step number 2.
Setup another Page Group in Portal to be the Page_Group_INTERNAL.
I figure if Apache can setup Virtual Hosts pointing to Independent parts of the File System without be shared. I was expecting some kind of custom configuration where I can setup httpd.conf to point to some specific PageGroups to make sure
www.abc.com => Page_Group_External
never share information with:
intranet.com => Page_Gorup_Internal
My TAR was very quick closed with the Argument that is not what It supposed to do.
Since a virtual host is a common thing to do on Linux and Apache, I wonder if You guys could list this as one of the default features to have multiple virtual domains assosiated with Page Groups that they never talk or share Resources I think that would be really great.
In the mean time I guess we have no option but to put a password for every internal page or take the risk of share our Information to the Internet. Perhaps designate another box with Oracle Portal but In that case Is not really cost/bennefit to use a killer technology for our external site since we just have no more than 30 pages.
Anyway just figure drop you guys a note any advise will be really appreciated.
Best Regards Dino.

Hi Martin,
1. To change the target URL of KM resources you can to the following:
Access the URL Generation Service Configuration by navigating to:
System Administration -> System Configuration -> Knowledge Management -> Configuration
Content Management -> Global Services -> URL Generator Service
Change the Host property to "portal.company.com".
2. You change the Port by opening the Visual Administrator and going to : Dispatcher -> Services -> HTTP Provider
Change there the "Ports" entry from (Port:50000,Type:http)to (Port:80,Type:http). Then go on "Save".
3. To remove the "/irj" from the portal URL you can create a index.jsp with the following content, and save it in the J2EE Documentation folder:
<Drive>:\usr\sap\<SAPSID>\JC<J2EE_instance_number>\j2ee\cluster\server0\apps\sap.com\com.sap.engine.docs.examples\servlet_jsp\_default\root
<%
//Send the redirect using server redirection (not client script)
//This will also send the HTTP GET parameters
String queryString = request.getQueryString() ;
if (queryString==null ) {
response.sendRedirect
("irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default") ;
} else {//redirect with HTTP GET parameters
response.sendRedirect
("irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default?" + queryString) ;
%>
Hope this helps,
Robert

Restrict DNS zone transfers to specific hosts?

Is it possible within Server Admin to restrict DNS zone transfers to specific hosts? If not, can the allow-transfer statement be added to /etc/named.conf without breaking the ability to use Server Admin to administer DNS?
Thanks,
Bob
XServe Dual Processor Xeon server Mac OS X (10.4.8)

you can add the statement... it should not break Server Admin.
While you are there, you may want to add forwarders for efficiency.
Add the bold code
options {
directory "/var/named";
forwarders {
0.0.0.0;
0.0.0.0;
forward first;
recursion true;
replace 0.0.0.0 with your ISPs name servers
Jeff

Seperate logs for software virtual hosts?

As the subject says, I'm trying to create seperate web logs for software
virtual hosts, under iPlanet Web Server 4.1.
I found a brief mention of using the "host" parameter for <Client> tags
in the docs, but this just seems to write the same data to all logs
regardless of the client tags.
Relevant bits from obj.conf:
Init fn="init-clf" testlog1="/tmp/access_vh1" testlog2="/tmp/access_vh2"
[ other stuff snipped ]
<Client host="firsthosturl*">
AddLog fn="common-log" name="testlog1"
</Client>
<Client host="secondhosturl*">
AddLog fn="common-log" name="testlog2"
</Client>

Tim Lavoie wrote:
I found a brief mention of using the "host" parameter for <Client> tags
in the docs, but this just seems to write the same data to all logs
regardless of the client tags.
Relevant bits from obj.conf:
Init fn="init-clf" testlog1="/tmp/access_vh1" testlog2="/tmp/access_vh2"
[ other stuff snipped ]
<Client host="firsthosturl*">
AddLog fn="common-log" name="testlog1"
</Client>
<Client host="secondhosturl*">
AddLog fn="common-log" name="testlog2"
</Client>I'm not sure you're allowed to define multiple log files in a single
Init line. Try creating a seperate Init line for each log file (don't
forget the format line as well).
Joe McCabe There's a group of people that worship the number zero.
AOLScape These days nothing's sacred.

How to change DNS zone, or how to host email outside of BC

I have BC from Creative Cloud Suite, so I have the cheapest possible plan for BC. Meaning I don't get any email hosting. So I was looking to host email outside of BC. I looked it up on google to see if it could be done (I'm really new with all this hosting stuff!), and I found that if you change the DNS zone and MX records to certain things you could. I had to delete the MX record I had set up prior to finding out BC won't host my email, and I went to set up an Advance DNS Records.. But I'm not sure what to do! There's a lot of information I'm not sure about, and I don't know what goes where!
I'd like to have godaddy host my email, and what I found is that I need to change my DNS zone to: mailstore1.secureserver.net and change MX records to 0 smtp.secureserver.net 10 mailstore1.secureserver.net
I may end up finding somewhere else to host email at a later point, but right now I just want to try to figure out how to do this so I'll be able to in the future. Any and all help is appreciated! Thank you

Hi
All you need to do is go to Admin > Site Settings > Site Domains and activate your new domain. You’ll have to enter an MX record for e-mail to be setup, which will be provided by godaddy.
Here’s a similar article on the same topic:
http://forums.adobe.com/message/4997019#4997019
Let me know how it goes

Mountain Lion mail virtual hosts?

In Lion Server Admin app we could enable Postfix virtual hosting and list the domain names we wanted to receive mail for.
With no Server Admin app in Mountain Lion is there a GUI way to do this or must we take our chances with co-managing the Postfix configuration files and dbs ourselves?

Just spotted it!
In Server >> Mail Settings >> "provide mail for:"
Add to list

Help with Preference pane DNS settings for Mail

I have a mail (not Apple Mail) issue with my Entourage Mail. I keep getting
the following error message and I have verified the server settings in my
mail accounts are correct for ATT that uses pop.att.yahoo.com. I manage to
get mail most of the time but I still get the following error message:
Error Description
Error:
Entourage cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct.
Explanation:
Could not retrieve mail
Error: -1370
My System Preferences/Network/Advanced/DNS point to my 2wire Gateway combo
modem/router. The router is set for Automatic DNS. I tried changing it to manual
and it did not works any better.
If I change the DNS setting in the preference pane in OS X, will it really use that
DMS address and bypass the router?
I played around with the namebench utility
http://www.macupdate.com/info.php/id/32784/namebench and each time you
run it, namebench makes a better recommendation - saying something is faster
than the previous recommendation.
I am lost on what I need to do correct the Network pane of my System Preferences.
Should it point to the router or to good DNS?
I do not think this is a Microsoft Entourage issue.
Have others seen this issue or is unique to my setup.

Going to sleep on and see how it works in the morning.
The problem is solved and I have checked the Yes button that my
question has been answered. The following is a copy of a posting
two days ago to the Microsoft Entourage group that should work
just as well for Mail users.
If you are tied of getting the following Entourage error
message -3170 over and over again, read on.
Error:
Entourage cannot find the server. Verify the server information
entered correctly in the Account Settings, and that your DNS
settings in the Network pane of System Preferences are correct.
Explanation:
Could not retrieve mail
Error –3170
Thanks to a tip from Diane Ross I have gone two days without
getting the error message.
First, I know the Account Settings for my ATT DSL service
have been correct for some time and have not changed.
The short version of the fix that worked for was to open
the OS X 10.6.3 (Snow Leopard) System Preferences/
Network/Advanced/DNS panel and add some better Domain
Name Servers from my location.
The default (or before) OS X setting was:
DNS Servers: Search Domains:
192.168.1.254 gateway.2wire.com
Note both were dimmed. The server listed tells OS X to use
the ATT provided combo 2wire modem/router for my DSL service.
The change that seem to have worked for me was to leave the
Search Domain the same; however, I added some good servers that
bypass the 2wire gateway with its automatic DNS setting.
DNS Servers: Search Domains:
208.67.220.220 gateway.2wire.com
208.67.220.222
65.68.49.51
192.168.1.254
I found the ‘good’ or better DNS Servers by making several runs
using the free Google utility called namebench 1.2
<http://www.macupdate.com/info.php/id/32784/namebench>
This utility takes some time and will make suggestions from your
location. If you add the namebench recommendation and run it
again it will find a better recommendation. I had to make several
runs to find the better DNS Servers for my location. The first or
primary is called OpenDNS, the second is a backup for the OpenDNS
and the third is SBC Global TX now owned by ATT and I live in
Texas. Note I ended with the default IP address.
FYI, I tied using the selected servers in the 2wire gateway in the
manual mode rather than the default automatic mode and it just
did not work right. Some pages would not open and others were
slow. For this reason I run the router in the automatic mode for
DNS and control things using the OS X Network preference pane.
The addition of preferred DNS Servers in my Preference seems
to have slowed down and hopefully stopped Entourage 2008
version 12.2.4 -3170 error messages.
Message was edited by: aRKay

DNS: Zone name vs. Host name question

My little office OSX Server setup has been working fine, but I realized my DNS setup was a little weird. I think the primary zone and first host machine record were setup during the initial install/setup process, and it doesn't seem to match what Hoffman recommends in his excellent DNS Setup guide.
My primary zone was named "files.example.com", and my server host record was also named "files.example.com". Everything seemed to work, but I realized when I wanted to add some additional hosts and aliases, I was getting something like "mail.files.example.com", when what I wanted was "www.example.com".
Hoffman, and others, recommend trashing the default zone and records, and making a new zone named "example.com", then making a machine record for the server, "files.example.com".
That makes perfect sense, except I don't understand one thing: how, with this setup, can I get the dns to cough up an ip address for hostname "example.com"? Can I make a machine record with a blank hostname, thus yielding a hostname that is the same as the zone name?
Thanks.

RobertNichols wrote:
My little office OSX Server setup has been working fine, but I realized my DNS setup was a little weird. I think the primary zone and first host machine record were setup during the initial install/setup process, and it doesn't seem to match what Hoffman recommends in his excellent DNS Setup guide.
My primary zone was named "files.example.com", and my server host record was also named "files.example.com". Everything seemed to work, but I realized when I wanted to add some additional hosts and aliases, I was getting something like "mail.files.example.com", when what I wanted was "www.example.com".
Hoffman, and others, recommend trashing the default zone and records, and making a new zone named "example.com", then making a machine record for the server, "files.example.com".
That makes perfect sense, except I don't understand one thing: how, with this setup, can I get the dns to cough up an ip address for hostname "example.com"? Can I make a machine record with a blank hostname, thus yielding a hostname that is the same as the zone name?
Thanks.
Apple setup wizard creates a zonename like files.example.com i.e. the same as the host name. I totally agree with Hoffman this is wrong (and I reported it as a bug to Apple) but that is the way Apple do it until 10.7 at least.
I therefore do the same as Hoffman and trash Apple's auto-created zone and do it myself.
Note: The auto-zone format used by Apple will work and might be 'good enough' for a small simple internal only setup, but if your doing a more complex multi-server setup and especially if your going to do split-horizon DNS, it is a terrible setup.

DNS settings for virtual host 10.6 server

We have just gone through a rebranding exercise, i.e. the company name has changed from 'mycompany' to our 'ourcompany'.
For various reasons we have decided to not rename our complete setup, but rather add a virtual host for our mail server including a second primary DNS zone for the new domain 'ourcompany'.
We are hosting our website externally, however since we added the second primary DNS zone incl. an A record (www) pointing to our external website hosts IP for 'ourcompany', workstations on our LAN can no longer access the website.
Running DIG for 'www.ourcompany.com.au' results in the correct A record IP address being shown, but it is still not showing in any browser – we also made sure we emptied our caches.
Although we thought this should work relatively easily, we are now totally confused as to the additional primary zones general settings... currently we allow zone transfer and provide an entry in the nameserver section.
Any ideas as to what might be going on here would be greatly appreciated.

Mr. Hoffman,
Than you very much for your reply - unfortunately, despite studying and testing your advice (incl. wesbite) we seem to not get much further.
Please find our comments inserted below...
MrHoffman wrote:
FWIW, both mycompany.com.au and ourcompany.com.au are real and registered domains; I'll presume they're not the domains you're migrating from or to. Accordingly, I'll use example.org for your old stuff, and example.com for your new stuff; the example domains are RFC-reserved for this usage.
Correct we are not using my bad example domains.
Each host should have one A record (and one AAAA record, if you have IPv6 active), and one of the more common errors in these migrations is setting up an A record for each new domain that might arrive; each host has one A (and possibly one AAAA) record, and that's the canonical name for that host. Externally, that'll probably be the latest name in any sequence (such as www.example.com), and all previous names (including www.example.org) will have CNAME entries.
To clarify do you mean the following: internally we should not have more than one A record for each host... i.e. one for example.org and one for example.com and presumably any other subdomains should be CNAME records?
2. externally we should change the A record for www.example.org to a CNAME record and create a new A record for www.example.com;
Internally (and here's why having a different domain inside is handy) use one of the old names; use example.org, for instance. This means you can use the public DNS services for the external web sites and resources; your internal DNS servers receive the requests for example.com hosts and go "duh, lemme ask somebody else for that", and that somebody else is the (public) DNS server your external DNS services for example.com hosts.
Exactly what we had initially done - basically we (naively) thought we could get away with only relying on external DNS translations... however that resulted in mail clients on our LAN loosing their connection every 5-10 minutes, thus we decided to setup another primary DNS zone which fixed that problem but created the other.
Please also note we have created a subdomain admin.example.com which properly resolves to the CMS backend - btw. from within this backend you can then preview the any page on the regular website with their non www. URLs.
Since the current setup resolves to the correct IP address I wonder if it could be a problem with the .htaccess rewrite rules the web developer has setup to remove the www. ... or is this too far fetched?
The usual trigger for not reaching the external A (or AAAA) records is either a stale cache on the particular client (for translations inside the Time To Live (TTL) values for the old DNS translations, or pending a local cache flush on each client), or (and this is more common) confusion over authoritative DNS servers; you have your internal DNS configured as authoritative for the new www.example.com domain, and also authoritative for the old www.example.org domain, and your external DNS is also authoritative for (probably) both domains. Internal requests get as far as the internal server, and get an authoritative translation (possibly being "no such host"), and don't go any further.
Safari & Firefox present with 'Server not found' errors.
So we are still stuck thus any further advice would be much appreciated.

Routing DNS requests in a zone to a default host

Hi,
What I'd like to do is to direct all DNS requests for non-existent hosts to a single host by default. So even if I haven't defined a hostname in my zone, the request will still resolve (to this default host). Any ideas?
Ben

It's possible to do via wildcard DNS, but you cannot do it via Server Admin (it doesn't permit the * for the wildcard name), therefore you have to get under the hood and edit your zone file directly.
You'll need to find your zone's domain file in /var/named and add a line like:
* IN A 1.2.3.4
(where 1.2.3.4 is, obviously, the IP address you want all unknown addresses to point to).
You'll also need to increment the serial number in the SOA record near the top of the file (otherwise your change won't be noticed)
Restart named (e.g. via killall -HUP named or via Server Admin), and now any lookup for an unknown host will return the specified address.

How to configure multiple virtual hosts for the same context root /

Hi,
I am using Glassfish V1 U1 - b14 on Solaris.
I am trying to configure two applications to be mapped to the / root context, each one in its own virtual host.
Two things I have noticed:
1. I have to manually add virtual-hosts="hostId" in domain.xml/application-ref ... looks like just simply deploying the app does not do that although the application is set as default for its particular virtual host. Is this a bug?
2. Although I have set for each virtual host the default web-app correctly, and they both respond fine, I cannot map both of them to the / context. The second application (chronologically deployed) does not respond when called with the / context ....
Any ideas? Is this a bug again?
Regards,
Rares
Message was edited by:
raresp

Wow, that's a shame. All mighty Application Server and two different apps on two different virtual hosts are considered ambiguous to have the same context root definition.... Fair play to Tomcat and 90% of the rest of servlet containers!
In my case I have the same EAR we are planning to deploy to many (up to 30) virtual hosts. Faking different context roots for each deployment will bring unnecessary overheads...
Should I file a bug or feature request?
Thanks again for your answer, although you're basically saying it is not possible I will wait and look a while for a possible solution before bringing this topic to a conclusion.

Mod_rewrite not working for virtual host nor .htaccess

I've been tearing my hair out trying to implement mod_rewrite on my Leopard Server. I have finally been able to get mod_rewrite to log what it does, but that has only shown that it DOES periodically respond to a /server_status request from the server itself, but any request to the virtual host (which is otherwise working) does not result in mod_rewrite being 'triggered.' I've tried all the usual suspects, in just about every permutation and combination:
1) .htaccess in all its guises and Override All;
2) RewriteEngine On;
3) http.conf, the virtual xxxx_80_virtualhostname.com.conf;
4) Options All -Includes -ExecCGI +MultiViews -Indexes +FollowSymlinks;
5) other less credible ideas gleaned from the Apple discussions and the web.
If I had to summarise the effect, it's that
a) mod_rewrite is on (as shown by the regular /server_status entries in the rewrite.log);
b) xxxx_80_virtualhostname.com.conf is read when the virtual host is turned on (because the site is active and can be turned off, at will);
c) any mod_rewrite and Options entries in the vistual host xxxx_80_virtualhostname.com.conf seem to be being studiously ignored, even though the .conf file is being read and used.
This part of http.conf is what seems to turn on the logging:
<IfModule mod_rewrite.c>
     RewriteEngine On
     RewriteLog /private/var/log/apache2/rewrite.log
     RewriteLogLevel 9
</IfModule>
Here's the section of xxxx_80_virtualhostname.com.conf:
<Directory "/Library/WebServer/com.VirtualHostName">
     AllowOverride All
     <IfModule mod_dav.c>
          DAV Off
     </IfModule>
     Options All -Includes -ExecCGI +MultiViews -Indexes +FollowSymlinks
</Directory>
<IfModule mod_rewrite.c>
     RewriteEngine On
     RewriteLog /private/var/log/apache2/rewrite.log
     RewriteLogLevel 9
     RewriteRule ^/Tom.html$ /Mary.html [R]
     RewriteCond %{REQUEST_METHOD} ^TRACE
     RewriteRule .* - [F]
</IfModule>
This is a variant of the .htaccess file:
RewriteEngine on
RewriteBase /
RewriteRule ^/Tom.html$ /MARY.html [R]
It makes no difference whether the RewriteBase is present in the .htaccess or the xxxx_80_virtualhostname.com.conf, or both.
No amount of pass-though [PT] or redirect [R] has any effect, either.
I do have Lasso 8.5 installed, but the developer says that Lasso should have no effect on the proper functioning of mod_rewrite.
mod_rewrite is working (i.e. it's on, as shown by the /server_status entries in the log and that the log is being updated), but it is also not working (in that no matter what I put into xxxx_80_virtualhostname.com.conf and/or .htaccess, there is no entry in the rewrite.log nor in the system logs).
Hence, I'm stumped. Any suggestions would be very, very welcome.

Never mind. I discovered that Server had created several versions of the virtual host .conf file in the sites folder (I've no idea why, when, or how it would do that). They all had different numbers and so were well hidden within the dozens of other .conf files. Once I a) found the right .conf file for the virtual host, and b) deleted the rest from the sites folder, my mod_rewrite code worked fine.
Hence, if you find that mod_rewrite is working, but not for a particular virtual host, make darn sure that there are no errant .conf files for the domain and, if there are, that you're editing the correct one.

Virtual Host (localhost) + Wamp 2.1

Hello
I'm trying to test a local URL like xxxxx.localhost or loclahost / xxxxxxx
This does not work.
I read this post related to this topic:
http://blogs.adobe.com/edgeinspect/2012/06/19/shadow-xip-io-virtual-hosts-workflow-simplif ied/
But I do not know what to do.
Thank you for your help.

No change.
Changes in the file are in bold and italics.
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.2> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.2/mod/directives.html>
# for a discussion of each configuration directive.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
# server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths to avoid confusion.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
ServerRoot "c:/wamp/bin/apache/apache2.2.17"
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
#Listen 80
Listen 0.0.0.0:80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_alias_module modules/mod_authn_alias.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
#LoadModule disk_cache_module modules/mod_disk_cache.so
#LoadModule dumpio_module modules/mod_dumpio.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule filter_module modules/mod_filter.so
#LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
#LoadModule ldap_module modules/mod_ldap.so
#LoadModule logio_module modules/mod_logio.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule mem_cache_module modules/mod_mem_cache.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule ssl_module modules/mod_ssl.so
#LoadModule status_module modules/mod_status.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule unique_id_module modules/mod_unique_id.so
#LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule version_module modules/mod_version.so
LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule php5_module "c:/wamp/bin/php/php5.3.5/php5apache2_2.dll"
<IfModule !mpm_netware_module>
<IfModule !mpm_winnt_module>
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User daemon
Group daemon
</IfModule>
</IfModule>
# 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin admin@localhost
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
ServerName localhost:80
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "c:/wamp/www/"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
    Options FollowSymLinks
    AllowOverride None
    Order deny,allow
    Deny from all
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "c:/wamp/www/">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    #   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.2/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    #   Options FileInfo AuthConfig Limit
    AllowOverride all
    # Controls who can get stuff from this server.
#   onlineoffline tag - don't remove
    Order Deny,Allow
#   Deny from all
    Allow from all
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
    DirectoryIndex index.php index.php3 index.html index.htm
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
    Order allow,deny
    Deny from all
    Satisfy All
</FilesMatch>
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "c:/wamp/logs/apache_error.log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel debug
<IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
      # You need to enable mod_logio.c to use %I and %O
      LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "c:/wamp/logs/access.log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "logs/access.log" combined
</IfModule>
<IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://localhost/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "cgi-bin/"
</IfModule>
<IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock logs/cgisock
</IfModule>
# "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "cgi-bin">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
<IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    AddType application/x-httpd-php .php
    AddType application/x-httpd-php .php3
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://localhost/subscription_info.html
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#EnableMMAP off
#EnableSendfile off
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf
# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf
# Language settings
#Include conf/extra/httpd-languages.conf
# User home directories
#Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts (STE)
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
#Include conf/extra/httpd-default.conf
# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
#       starting without SSL on platforms with no /dev/random equivalent
#       but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
#NameVirtualHost 127.0.0.1
#<VirtualHost 127.0.0.1>
#        ServerName localhost
#        DocumentRoot "C:\wamp\www"
#</VirtualHost>
NameVirtualHost 192.168.1.98
<VirtualHost 192.168.1.98>
        ServerName 192.168.1.98
        DocumentRoot "C:\wamp\www"
</VirtualHost>
Include "c:/wamp/alias/*"

DNS zones for Mail virtual host

Similar Messages

Maybe you are looking for