Web Hosting Talk







View Full Version : How hard ?.


-Edward-
11-07-2000, 02:20 PM
How hard is it for a host to enable wildcards?.

And do they need certain settings to enable them to?.

kunal
11-07-2000, 02:27 PM
I dun think it is very difficult. Its just adding one extra line in the httpd.conf file. I think.

-Edward-
11-07-2000, 02:32 PM
*scratches head* Wonder why HostRocket say i need more info and its a week since i asked.

JonnyQuags
11-07-2000, 02:55 PM
When I wildcard I just add

* IN CNAME domain.com.
to the dns file.

Seems pretty easy :)

MattF
11-07-2000, 03:23 PM
Unless they are using a Shared IP system there should be no need to edit the Apache configuration, just the DNS.

Brendan at HostRocket
11-07-2000, 03:34 PM
Hi,

We did make that change to the DNS file, but I am pretty sure alabanza has some effect on getting it to work, as one of their support guys said something to me along those lines before. I have emailed them about it and havent gotten a response. You can try it out now as what we think needs to be done has been done, but we havent gotten back to you yet because we havent gotten the final word from them.

-Brendan
brendan@hostrocket.com

kunal
11-07-2000, 03:44 PM
But should'nt you guys have told Technics about what was happening? And anways, who cares wether it is a alabanza problem or not. Technics is dealing with you, not alabanza. Its your responsibilty to make sure, things come up and run ASAP.

-Edward-
11-07-2000, 05:27 PM
does http://www.you.flashtechnics.com or http://you.flashtechnics.com work for anyone else?. If this is a problem with alabanza could i be moved?. Sorry for asking here.

Félix C.Courtemanche
11-07-2000, 05:39 PM
I feel that some technical support is being carried here as much by teh customers and the host itself. I do not feel too comfortable with this and I would like to see it stop.

Wildcard is a matter of DNS and httpd.conf, depending what exactly you are tying to achieve.
domain.com .... [some more SOA here]
* IN A 123.123.123.123

would provide anything directed to domain.com to that IP. However, if your httpd.conf file is not configured to accept wildcard (alias *.domain.com) that will not work or display your default home page.

Also note that as with any other DNS changes, there may be a 1 day delay if your own ISP cached it before you asked for the change. A ISP will cache a positive or a negative answer to any request, so to save further processing speed. It is annoying when playing with the DNS a lot, though.

-Edward-
11-07-2000, 05:42 PM
Sorry Felix. I was just asking a question about wildcards i dont fully understand them but im getting the idea now.

Chicken
11-07-2000, 07:55 PM
Originally posted by Félix C.Courtemanche
I feel that some technical support is being carried here as much by teh customers and the host itself. I do not feel too comfortable with this and I would like to see it stop.

Agreed. Asking a general question is fine, but naming the host and then them replying here is not. I know it is hard when the host and the client are members, but try to keep specific replies to clients off the boards (as well as specific comments directed at hosts).

Note: Hosts and their clients are free to discuss topics here (don't misunderstand me), but let's try to keep converation and tech support seperate.

Ohhhh, and DNS'd wildcards don't just automatically work. Yes, you set up the DNS (see above), but then there is some server side stuff that has to be done. Different systems (such as automated Alabanza), might have some issues. I don't know either way with Alabanza. Even a wildcard set to an IP address will require a script of some sort to handle the redirection. Things won't work without this (or at least some way of handling redirection of the subdomains).

[Edited by Chicken on 11-07-2000 at 07:00 PM]