Problem: Some individuals' ISPs occasionally can't resolve one of my virtual hosts on a LAMP installation. Ubuntu 10.04 LTS, Apache 2. I'm looking for hack that can do it by IP.
Background: On this machine are a number of virtual hosts:
default.example.com subdomain1.example.com subdomain2.example.com subdomain3.example.com problemdomain.example.com
Which are really housed in:
var/www/default.example.com var/www/subdomain1.example.com var/www/subdomain2.example.com var/www/subdomain3.example.com var/www/problemdomain.example.com
Occasionally people from some ISPs cannot get to one of the domains, today it's
HOWEVER these users CAN route to the server via its IP address and receive the default server root landing page:
WHICH takes them to 'default.example.com'
Note: The directory i want them to get to is ABOVE the current directory, and directory walking is off.
IDEA 1: If they can get to the IP of the server and I make a landing directory (default.example.com/foo), can I somehow redirect them to another folder on the server thereby getting them to the right place? How would I do it? * Remember, DNS is not working, so I would think a 301 redirect won't work because it will just tell their browser to look for 'problemdomain.example.com' which they cannot resolve.
Layspeak rephrasing: Is there a way to tell apache "Hey, if someone requests directory 'foo' on the main server's default web landing page:
THEN take them to this other virtual host on the server
Or, is there something like using:
or some other 'force' to do it? It's not realistic for me to ask end users who have troubles to add hosts entries on their system. Just some way so that for those rare occurrences that DO have a problem I can say something more helpful than "just try a computer on another web connection".
Much obliged for any help.