You can always add different (internal) IP addresses to your IIS server and make each such IP address correspond to the differently named domain setup. This would make your internal IIS server now DNS independent, while keeping the virtual host setup intact - arguably that keeps it a bit cleaner in the sense, that your Apache server doesn't need to know anything about the virtual folders on your IIS machine.
By the way, regular DNS changes should not take several days to ripple, if you prepare a little bit for the change.
step 1 - a few days before the changeover: set the affected host DNS entries get a short TTL, say 5 minutes or so.
step 2 - when you want to change: change the DNS entries as per usual, leave the very short TTL in place, just in case you accidentally screwed up, and need to change IP addresses again.
step 3 - a few days after everything is running well: change the TTL to something longer
While a very short TTL is not always accepted by ISP's, it gives you a fighting chance. For example last time I changed DNS entries with a short TTL, Shaw at least refreshed in 30 minutes. Definitely better than hours or days.
And you want a very short changeover is "A good thing" for several reasons:
* minimize the time of having to run 2 systems in parallel, or having the system unavailable to some people
* allow you to fall back to the old setup quickly, if the new one is really messed up
* recover from a typo for the new setup more quickly
Good luck! I hope this is worth the trouble, since you seem to be doing this mostly to save an IP address. Depending on your situation, it may actually be easier to get an additional IP address. Some ISP's don't charge that much extra for it.
Have fun!
....Niels
Shawn wrote:
Found yet another problem...
The IIS server in question is using named virtual hosts to provide a few different web sites, for two domains, and a couple of sub domains....
This ought to be REAL fun... NOT.
It'll probably be easiest (for me at least) to remove the virtual hosts from the IIS server, and point the Apache server at appropriate sub folders...
This is beyond my skill with Apache, but I'll keep digging. Any insights are appreciated...
Shawn
On Friday 01 October 2004 01:31, Shawn wrote:
I've been reading over the Apache rewrite rules and the URL Rewriting guide (http://httpd.apache.org/docs-2.0/misc/rewriteguide.html), but seem to be missing the solution to my particular problem.
I need to set up an IIS server on my network, and allow access to it via
it's own domain (for instance, http://www.newdomain.ca). Part of the
solution is to set up a named virtual host for the domain, and I've done
that. What I'm missing is how to tell the virtual host that the document
root is on a different server, and to mangle the URLs accordingly in both
directions so web pages and/or redirects happen properly.
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
