Is there a way I can use ISPConfig to park domains without activating then manually on the control panel? Something similiar like opensourceparking.com where the domain users just points to your DNS serves and it starts resolving
A script that actives a domain on ISPConfig or autopark. Now: 1.Client registers a domain, it gets registered with a default DNS which is poiting to the ISPConfig server. 2.Client sends me an email, please activate the parking for this domain. 3.Me, goes to the control panel and puts that domain on a hosting parking plan i created, the domain shows the default page which i created. What i want. 1. Client registers a domain, it gets registered with a default DNS which is poiting to the ISPConfig server. 2. ISPconfig detects that the domain is using his DNS and resolves queries to the default page. 3. Me. is in bed sleeping, i dont have to active the domain and client is happy he doesnt has to send me an email. I know this can be done, but dont know exactly how. Opensourceparking.com works like this. You point the domain to this DNS and it shows their page.
If all domains shall point to the same site, the easiest way will be to create a vhost for "*" manually in your httpd configuration file that accepts all domains. So there is nothing to be configured at all when a new domain is added.
Just like that ? Nothing else? That is really strange. I have posted the same question on at least 4 forums and even experts did not knew how to acomplish this even when to me it also seems a very simple task, i just dont know which config to open on the server. Could you be more specific on what to put on the httpd configuration? Thanks
What i do myself in that cases: i create the web for that client within ISPConfig. That website is forwarded to a webpage on my server with a message like: Companyname This domain has been registered on behalf of our client. For more information visit www.myhostingcompany.com). (or something like that).
Thats exactly what i dont want to do. Thats nice if you have a one domain, but if you register 100 domains a day its a pain in the ass. I want a automatic parking.
I can understand that, but for me it is fine, as i do not register so much domain names as you do. I hope you'll find a solution which is nice for your business.
I would try it like this: <VirtualHost _default_:*> DocumentRoot /www/default </VirtualHost> This will show the page(s) in /www/default/.. if no other vhost for this domain can be found. Or if you want to do this for just one IP address: <VirtualHost 192.168.0.100:*> DocumentRoot /www/default </VirtualHost> This is similar like the sharedIP definition in ISPConfig. You may even reuse the sharedIP page in ISPConfig for this.
I will try that right away except i have a problem. I dont seem to find the apache files. I read on the here its on /etc/apache2/vhosts/Vhosts_ispconfig.conf But i dont have those. I dont even have the apache2 folder. I uses the CentOs perfect Setup.
Yes thanks its on etc/httpd/conf/vhosts/ On the etc/httpd/conf there is httpd.conf and on etc/httpd/conf/vhosts/ is the Vhosts_ispconfing.conf The one I have to play is the one from ISPConfig right? Also regarding all this i posted the question on an Expert Paid Forum and i got this reply. Its somehow similar to here except they said a config about WildCard too. I hope this helps everyone, and if now someone can guide me to do this in ISPconfig that would be great. Im trying myself too. Two step process 1) Wildcard DNS, after the users registar a domain they will need to have the registar list your name server(s). Then on your ISPConfig you will need a BIND Wildcard DNS Entry, so that any incoming request get a default response if there is not a unique response for them. http://www.debian-administration.org/articles/358 ( best reference ) 2) Setup apache to answer for any domain name. See the first link I posted, for the details basically you modify the ServerAlias entry. http://www.debian-administration.org/articles/358 1. Edit Wildcards - look at Wildcard DNS section of http://www.debian-administration.org/articles/358 Have a *.com. record in your Bind config. if you need .org. then add that too. I am not sure if *. ( for any TLD) would work. 2. Edit apache files See - Apache Setup section of http://www.debian-administration.org/articles/358 I do not think you would have to worry about the mod-rewrite - I think that maybe for something more complex. Thanks, Mark
I'd put the custom configuration into /etc/httpd/conf/httpd.conf because /etc/httpd/conf/vhosts/Vhosts_ispconfig.conf will be overwritten each time you change anything in ISPConfig. Do you run your own nameservers, or does your domain registrar take care of that?
