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.

Similar Messages

Apache virtual host with OSX Server?

I have been running OSX Server for a while now, and just recently I decided to get McMyAdmin for my Minecraft server. The web client for McMyAdmin runs on port 8080, but I wanted it on port 80. I wanted to use it with my domain, so I just created a sub domain and pointed it to my server. The problem is that OSX Server apparently doesn't let me use port 80, even when websites are turned off. I decided to delete Server and just use plain apache. This worked until I realized that my website was only accessible locally. I have all the correct ports forwarded, etc. But I get the error:
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received from another proxy server or the destination origin server.
when I try to connect from outside my network. This is probably just some simple thing I missed but it would be nice if someone could just point out what I did wrong here. Back to the point, I want to know how to run the proxy to my web client on port 8080 AND ALSO run OSX Server with or without apache virtualhost.
Thanks in advance,
Eamon

Web is stupidly easy - Apache has extensive support for multiple virtual hosts in a single server and will happily support as many domains/hostnames as you can throw at it.
Mail is a little trickier since it needs to hook into some kind of directory server to validate user addresses.
Mac OS X's Open Directory does support this, but it's a little cumbersome (basically every user has to exist in the main Open Directory domain as well as having a secondary email address(es) in the other domain(s).
This can get especially tricky when you have users with the same shortname in different domains - for example if you give [email protected] a secondary email address of [email protected] and you then get a new user [email protected], you can't give the third 'joe' the address 'joe' in Open Directory since that's already taken. This means he'll have to login using different credentials from his email address. Confused yet? You bet.
If you're prepared to eschew Open Directory you can just use Postfix's built-in support for virtual hosting, but it's a little more complex to setup and support and is entirely command-line based (i.e. there's no GUI for setting it up or supporting it).
So, for that reason you might be prepared to setup multiple virtual machines for each domain. It really depends on how much the domains are related (if at all).

Virtual hosting on leopard server

Hello,
I have a leopard server on which I want to have two sites served from the same ip address port combination.
I am using the Server Admin tool bundled with OSX server to configure Apache.
I have created two sites in Sites tab. One has the name "mydomain.org" and the other has the name "machinename".
They are both configured to serve from the same local IP address.
The name "mydomain.org" is served by DNS and the name "machinename" is configured on the client's /etc/hosts file.
From what I know of virtual hosting, the web server receives a http header called 'Host' with the host name that was used on the browser, to select the files to serve. I have sniffed the http network packets from my client machine to the web server and seen this header set correctly to the hostname used on the browser.
The problem is that just one site is being served to both names. I want to select the site according to name.
What can I be doing wrong ?

Done it the hard way.
StuG

Configuring default web apps for virtual hosts

Hi,
This posting is meant save time for anyone trying to specify a default web app
for each of their virtual hosts (as opposed to specifying a default web app for
each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't tried
this on other platforms).
If you are trying to use the admin console to do this, give up. It's not possible.
The "Virtual Host/Configuration" window lets you specify everything about that
vhost configuration EXCEPT a default web app. (The "Default Web Application" drop
down menu will always have only one option to choose from: "none").
Instead, shutdown your server, and edit your domain's config.xml file manually.
Attached is an example config file that specifies that the web app "kz" should
be the default web app for the vhost "wl.kz.com", and that the web app "kahuna"
should be the default web app for the vhost "www.kahuna.com".
Hope this helps,
Brian O'Donnell
Lead Developer, Learning Network
[config.xml]

Hi,
Is it possible to configure default web appls for virtual hosts
with Weblogic 6.0 on NT platform? I tried to configure the configure.xml as Brian
did, it doesnot work. I am just wondering if there's any other possible way to
do this.
Thanks.
Mei
"Brian O'Donnell" <[email protected]> wrote:
>
>
>
Hi,
This posting is meant save time for anyone trying to specify a default
web app
for each of their virtual hosts (as opposed to specifying a default web
app for
each of their wl servers). This applies to weblogic 6.1, on NT. (I haven't
tried
this on other platforms).
If you are trying to use the admin console to do this, give up. It's
not possible.
The "Virtual Host/Configuration" window lets you specify everything about
that
vhost configuration EXCEPT a default web app. (The "Default Web Application"
drop
down menu will always have only one option to choose from: "none").
Instead, shutdown your server, and edit your domain's config.xml file
manually.
Attached is an example config file that specifies that the web app "kz"
should
be the default web app for the vhost "wl.kz.com", and that the web app
"kahuna"
should be the default web app for the vhost "www.kahuna.com".
Hope this helps,
Brian O'Donnell
Lead Developer, Learning Network

Strange info in "Bypass Proxy Settings for These Hosts and Domains"

For my Mac Mini my Network IP Address always has a self-assigned 169.254 number that I cannot change. Strangely, this same IP number is similar to info that is in the Proxies section (of Network Settings) under "Bypass Proxy Settings for These Hosts and Domains".
No matter what I do, this info (*,local, 169.254/16) appears in my Network Settings in the Proxies section under "Bypass Proxy Settings for These Hosts and Domains". (I tried removing the info and it would cause the "Configure Proxies" selection to default to "Always Use PAC File". Had to go back and retrash all the plist files to have Proxies go back to "Configure Proxies-Manually". Still, the info (*,local, 169.254/16) continues to appear in the "Bypass Proxy Settings for These Hosts and Domains" section and my IP address is always a 169.254 number.)
Comcast cable modem via direct hardwired Ethernet works fine with my other computer, so not the modem. Also, other computer does not have any info in the "Bypass Proxy Settings for These Hosts and Domains" section.
Installed a fresh copy of OS X 11.5 on a new hard drive. Still the same problem.
I posted this issue before but only got one responder and the problem still exists. Any clues? Somebody must know about this stuff. Help please.
Thanks

When your Mac wakes up, it does not yet have an IP Addresss. It wants to send a request to a Router for an apprpriste IP address to use now. But it needs to have an IP address (like a return address) to receive any messages. So, ... wait for it,
... it (your Mac) makes one up. There are rules that ensure it is a random address, but they always start with 169.254. It is on the same subnet with any low-order 16 bits This is the "self-assigned" range of IP Addresses. This address is only good for talking on a local network segment, for things like asking for a valid IP Address from a DHCP-enabled Router.
In most cases, on most networks, the 169.254 self-assigned IP Address is replaced by a valid Local IP Address such as 192.168.xxx yyy or 10.0.xxx.yyy so quickly that you never even see the 169.254 Address.
If you do see the 169.254 Address, it can be read as "Nobody will talk to me" or "Nobody will give me an IP Address". When you have this IP Address for more than an instant, you should suspect bad cables for Ethernet connections, bad signal strength or interference for wireless, Router configuration problems, or Mac configuration problems.
Mac configuration problems are often solved by using the "Assist Me" button is System Preferences > Network and choosing to set up again.
Another diagnostic is to try using Network Utility and the Ping function, and Ping-ing the address of your Airport base Station, often 192.168.0.1 or 10.0.0.1 or similar. This will tell you if the Router is reachable, or there are cabling/wirelss signal problems.
In this case, proxies are not an issue, and are simply a distraction from the real problems.

Configurational settings for data source in BI server

Hi Sdns,
Where can we make configurational settings for data source in BI server.
Advance thanks to replies.
karun

Go to T-code RSA13.
Search you desired BI system.
Right click on it and Display Data Source Tree.
There you can see all your datasource with BI as source system.
You can do the same for other source systems.
Double click on the datasource to see the fields and configuration.

"it's always DNS" - Need Help setting network/DNS settings for MacMini Serv

Well, I must admit defeat and ask for help. I've set up an Xsan or 2, but for the life of me cannot set up my mac mini server. My basic two problems seem to be these:
1) Service Order in System Preferences/Network
I want to run my private LAN through Ethernet, using a 10.1.17. IP range, and use my Airport Extreme Base Station (Technically a Time Capsule) for the Public ISP 192.168.1 DHCP service. Cannot get both to work. The only way I can get the server to work and to be able to login using Open Directory is to either set the Ethernet as Primary for both my client and server, in which case there is no internet service AT ALL for either. I have a sneaking suspicion it has something to do with either DNS or a few extra DNS entries in the ethernet or airport categories, but for the life of me I cannot find the right combination. Is there any way to have BOTH Ethernet LAN and Airport internet service?
2) Related to the first question, I think, is that my local FQDN (not registered, just meant for internal LAN use only right now) and DNS name only show up to my client computer in Server Admin, Directory Utility, Workgroup Manager if I DISABLE my airport card. Otherwise, they come up as <servername>.local and not the FQDN <servername>.editdog.com, and I cannot login using OD.
3) I'm not sure what happend to the Binding I used to have to do in OSX Server 10.5, but maybe that's the issue? I have the Peachpit OSX Server Essentials Book, and it's been less than helpful.
Any ideas out there?

bump

Best Practices for Virtual Hosting

I am providing hosting for a few churches besides our own and had some question regarding best practices.
My primary domain say is churchhosting.com with an A record "mail.churchhosting.com" pointing to my static ip. It also has a MX record to "mail.churchhosting.com" and a PTR record set by my ISP to "mail.churchhosting.com".
For the other sites I am hosting say "church1.com" and "church2.com", should I set their MX record to "mail.churchhosting.com" or have an A record "mail.church1.com" pointing to my static ip with a MX record to "mail.church1.com." and likewise with the "church2.com" domain.
What would the best practice be and the potential problems that either might present with the server?

Am I doing this correctly? I want to know how many SSL certs I need under the following:
In a similar situation, I think. I have multiple virtual domains setup. For example, company.com, company1.com, company2.com.
Mail Services General Settings show the host name at company.com. All the company.com, company1.com and company2.com are listed under Advanced > Hosting as virtual domains.
All these domains are on a single IP address. The DNS is hosted at godaddy and all MX records for company.com, company1.com, and company2.com are '0 @ company.com'.
All the CNAME records for mail.company.com, mail.company1.com, and mail.company2.com point to "@" and all the A records point to the same IP address. There is only one server.
I think what this means is that I've set it up so that all mail.xxx.com is routed to mail.company.com for all virtual domains. I want to use SSL certs for mail. How many will I need under this arrangement? Is it just one for mail.company.com or is it 3, one for each virtual domain?
Thanks.

How to properly setup virtual hosts on leopard server

I am not just new to leopard server but new to “server” as a whole. I have bought a 10-client leopard server and installed it on my old macbook couple of days ago because of the gui and seemingly ease-of-setup of a leopard server. I have watched and followed a tutorial on Lynda.com to install my server. Unfortunately, that tutorial focuses mainly on running a single web server. My main purpose of setting up the leopard server is to run multiple virtual hosts. Now my server (which has its own public ip address and I shall refer to it as just IP) is up and running but I seem not to be able to get virtual hostings to work properly. Below is a summary of what I have setup and I hope somebody from the community can take a look and point out what I have done wrong (thanks in advance):
- server setup as advanced
- dns settings:
o I am not sure whether a different zones should be setup for each domain, so I have opted to define 1 primary zone only and then define the other domain as a machine. For simplicity sake, I have only used two domains in the example below. I actually need to setup at least half a dozen.
o primary zone
• my1stdomain.com. is the primary zone name
• ns.my1stdomain.com. is the only nameserver
• mail.my1stdomain.com. is the only mail exchanger
• www.my1stdomain.com. as machine and IP as value
• www.my2nddomain.com. as machine and IP as value
• mail.my1stdomain.com. as machine and IP as value
• server.my1stdomain.com. as machine and IP as value
• ns.my1stdomain.com. as machine and IP as value
o reverse zone
• ip reverse mapping ns.my1stdomain.com.
- web settings:
o sites:
• I have defined the following 2 sites and point each of them to a different folder:
• my1stdomain.com
• my2nddomain.com
- I have setup dns at my domain registrar to reference ns.my1stdomain.com for both my1stdomain.com and my2nddomain.com,
I have no problem accessing www.my1stdomain.com but I couldn’t reach www.my2nddomain.com. and I have a hunch it has to do with my dns settings.

It sounds like there are two compounding errors here.
• www.my1stdomain.com. as machine and IP as value
• www.my2nddomain.com. as machine and IP as value
By definition, www.my2nddomain.com cannot be a record in my1stdomain.com's zone.
You MUST have one zone for my1stdomain.com (that contains my1stdomain.com's NS, MX, mail, www etc. records) and a SECOND, separate zone for my2nddomain.com that contain's its records.
Now the records in my2nddomain.com's zone may contain the same data (e.g. the same A record), or even reference my1stdomain.com (e.g. 'www.my2nddomain.com is a CNAME to www.my1stdomain.com), but they are separate zones.
Secondly.
I have defined the following 2 sites and point each of them to a different folder:
• my1stdomain.com
• my2nddomain.com
If you want to access the site via 'www.my1stdomain.com' (or 'www.my2nddomain.com') then your site needs to be setup for www.my1stdomain.com, not my1stdomain.com
As far as the web server is concerned, 'my1stdomain.com' is a completely different address (and therefore a different site) from 'www.my1stdomain.com. While most poeple set them to the same it is entirely appropriate and valid for them to be two different sites as far as the web server is concerned.
Therefore you need to change your sites' configuration to reference the 'www' version of its hostname.
If you want to run both 'my1stdomain.com' and 'www.my1stdomain.com' as the same site then add the other hostname under Aliases (this tells Apache what hostnames should map to this virtual host).
Try fixing those two elements and try again.
Finally, it's often far easier for others to debug this kind of problem when you talk in real names, not dummy ones. Telling us what the domains in question are, for example, would allow others to query DNS to see what values you're actually publishing, and would go a long way to answering the question for sure, as opposed to just speculation.

Problem with DNS and/or Virtual Host (works from inside, not from outside)

I am running several web sites (as virtual hosts) successfully on one Xserve (192.168.200), which are accessible internally and from the Internet (via forwarding port 80 on our firewall).
Now I am trying to add another web site (newmini.domain.com), which however is running on a Mac mini (also on the same subnet as the Xserve) at 192.168.100. What I did is make an additional entry under the Xserve's DNS for the domain (domain.com) (+ Machine..., pointing to 192.168.0.100). (I also made the necessary changes to the Mac mini's httpd and hosts configuration--no problem there).
Now, here's the strange thing: All computers on the subnet, whose DNS points to the Xserve, can see and browse newmini.domain.com fine. No problem. The computers ask the Xserve for the IP of the host in question, the Xserve says, "192.168.100", the request goes to the Mac mini, and it serves the web site as expected.
But this doesn't happen if the request comes from the Internet. Instead of seeing the Mac mini, the client sees the default web site of the Xserve... So it appears that somewhere, the virtual host part of the HTTP request is lost between our firewall and the Xserve.
Any ideas? Thanks.

It's not going to.
You say you've setup port forwarding on the firewall. Port forwarding only cares about the port number (80). It knows nothing about the nature of the request (e.g. the hostname that the web request is for). Therefore all extenal connections on port 80 get sent to the XServe. The newmini doesn't see the traffic at all.
If you only have a single public IP address you can only forward port 80 traffic to a single machine. Your options are to either use a different port number, or configure the XServe to proxy the connection to the mini (so now the traffic goes router -> XServe -> Mini -> XServe -> router), although that might not do what you want since it still places load and dependencies on the XServe.

Virtual Host on WebLogic Server 5.1

I need to configure my weblogic server 5.1 on windows 2000 server to make a virtual
host address.
How I can do it ????
Thanks a lot for any help.
Bye

Hi Andy,
I think a good approach for you would be to use a proxy server --
browser -> proxy that supports virtual hosting -> WebLogic
Use a proxy which supports virtual hosting, and which can have a separate
certificate bound to each virtual host.
That way you can do SSL between the browser and the proxy, and you can
have the proxy do cleartext to WebLogic.
This situation gets around WebLogic's limitation of allowing only one
certificate per instance of the server.
You could also use 5.1 as the proxy in the following manner:
Run 3 instances of Weblogic, each as a proxy server, each bound to a
different IP address and DNS name, having its own certificate --
one instance for aaa.com, another for bbb.com, and a third for ccc.com
Then have each of these three instances of WebLogic proxy to your "app
server" instance of WebLogic on the backend.
Hope this makes sense.
Joe Jerry
Andy Walker wrote:
Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

SSL with virtual hosting in Weblogic Server 5.1(WLS5.1)

Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

Hi Andy,
I think a good approach for you would be to use a proxy server --
browser -> proxy that supports virtual hosting -> WebLogic
Use a proxy which supports virtual hosting, and which can have a separate
certificate bound to each virtual host.
That way you can do SSL between the browser and the proxy, and you can
have the proxy do cleartext to WebLogic.
This situation gets around WebLogic's limitation of allowing only one
certificate per instance of the server.
You could also use 5.1 as the proxy in the following manner:
Run 3 instances of Weblogic, each as a proxy server, each bound to a
different IP address and DNS name, having its own certificate --
one instance for aaa.com, another for bbb.com, and a third for ccc.com
Then have each of these three instances of WebLogic proxy to your "app
server" instance of WebLogic on the backend.
Hope this makes sense.
Joe Jerry
Andy Walker wrote:
Hello,
I am tasked with implementing a virtual hosting situation that must
use SSL. It goes like this: https://www.aaa.com, https://www.bbb.com
and https://www.ccc.com all having separate IPs. These URLs must
forward the request to the same WebLogic Server instance. The problem
is each URL must have its own certificate while WLS 5.1 only uses one
certificate per instance.
I was thinking about using a proxy server such that all three Web
servers that would host the URLs would be sent to a proxy server which
would redirect to the WLS 5.1 instance.
My questions are, would this be feasible using WLS 5.1 as the Web
Server and again WLS as the App Server? How secure is this
arrangement? Is it preferable to use another vendor's software as the
WebServer(IPlanet, Apache)

DNS entry for DC not dynamically updating (Server 2008 R2)

Windows Server 2008 R2. I've got a single DC (I'm preparing to install the 2nd in the next few days). The host (A) record for the DC shows to be static for some reason. I changed the name of the DC recently, then brought down the Exchange server and rebooted
and it successfully connected again. I might have entered in a static DNS entry for the new server name before renaming the server, but I'm not sure.
I've tried to delete the static DNS record for the DC and then reload, but it continues to appear as a static entry. The mail server's DNS record still appears as a dynamic entry.
What am I doing wrong?
Noel Stanford Oveson
jeremyNLSO
MCTS, MCITP, CCENT, CNE, MCSE, CLSE
Berlin, Germany

Hello,
Like Mike suggested, it is normal that it is a static record.
However, if your DC with its new name is not updating its DNS record, check that "Register this connection' addresses in DNS" is checked on the DC's adapter and then run
ipconfig /registerdns using an elevated prompt.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Multiple IP vs Same IP multiple port for virtual hosts

Anyone have any recommendations or experience in setting up a virtual host that has a listener for each site?
The issue is when I have to restart a single site, I have to restart them all, because they are installed under the same listener/server.
I need a setup where I can install and manage each website (on the same box) on it's own listener/server instance so re-starting one site doesn't effect another.

Add a service in the Network preference pane. Select the network interface you want; e.g., Ethernet. Configure as desired. Apply and test.

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.

DNS settings for virtual host 10.6 server

Similar Messages

Maybe you are looking for