Well, first of all, thank you for all your answers and advices.
It is not questionable that this is out of the scope of DNS, and vegadns itself.
My point was just to have an uniformized interface to manage both regular DNS records,
and in the meantime the web redirections, all inside vegadns.
In my setup i fully let users add their own domains, and let them admin them, based on templates mapping to my servers.
But I just don't feel like having two interfaces, one to setup zones, the other to setup redirections.
I also definitly don't feel to edit anyfile myself by hand each time a redirection is changed .. (got 186 atm!)
In my case, i did not wanted (probably that was a mistake) to use any apache config related directives,
because :
a) i'm not using any db backend for apache
b) i'm not granting httpd.conf access to the ones who need these redirections.
c) i wanted to keep the thing as much integrated into vegadns' database as possible, thus each name server could also be a redirect server (provinding basic dns "load balancing" mechanism), as i'm replicating both db and data file on slave name servers.
d) i'm of course already using "zone-templates", and they do serv me well.. but i think they don't directly help me with this redirection thing.
I'm a bit sorry, as I think I led some of you in wrong directions, about what i was trying to do.. and mostly why ..
.. And yes, that text database thing is ugly that's for sure.
Anyways ..
Take care.
Rudolph.
----- Original Message ----- From: "Bob Hutchinson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 30, 2004 12:28 AM
Subject: Re: [users] dns to web redirection with vegadns ? mechanism and script proposal ..
On Saturday 27 November 2004 17:55, [EMAIL PROTECTED] wrote:In the past we had the case where we needed to add web redirection services
for some friends..
I've been googling to find out some ways to do so.. found only one sf.net .. but wasn't satified with it.. as it would require not using vegadns anymore..
So, one night, after long thoughs, i've decided to ask two friends to find
a way to, at first, to design a script that would handle any calls to it,
and redirect to the apropriate url, based on a simple file database.. Than,
publish the script, and see if someone would be interested to add some
"redirection" field to vegadns interface and database, that would only add
the apropriate fields in the database of the targeted domain..
After some tests, we came out with a pretty simple script, that uses (for the moment), a simple text file to figure "who goes where"..
In my further examples, i'll be using this general idea: some.url.domain.com needs to point to www.some.isp.com/some/dir/some.file.html
Also note, as pre-setup on my "main" company domain, i've created a generic
alias that will be used as cname for any url needed to be redirected..
Therefore: i made one Alias on my main domain like : redirect.mydom.com >
alias > 192.168.0.11
Than, in the zone of "domain.com", i created : record some.url.domain.com >
cname > redirect.mydom.com
The idea is that all redirections have to point to redirect.mydom.com.
Now, the apache is setup on 192.168.0.11 :
one spare ip for apache is needed, on my apache box, i'll use 192.168.0.11
here, with a very basic vhost definition (provided below)
---cut--- <VirtualHost 192.168.0.11:80> DocumentRoot /home/system/redirect/docs ErrorLog /home/system/redirect/logs/redirect-error_log CustomLog /home/system/redirect/logs/redirect-access_log common </VirtualHost> ---end of cut---
Use the Apache Redirect directive in your virtual host definition done
-- ----------------- Bob Hutchinson Midwales dot com -----------------
