wildcard virtual host

You'll notice I didn't write anything about DNS wildcards; that addition came from the second poster to the thread.

I don't believe in wildcard DNS, as I understand the problems it causes.

So I don't use it.

The problem with doing anything as a reseller is that you can't change the httpd.conf file, and depending on what your host allows, you may not be able to change DNS.

So if you can't get your host to help you with each of these as you need them, then you may have to go with the username method (using ~username).

Jeff
 
Hi there,

Thanks for your fast response.

Eventhoug I think I understand the main issue concerning the wildcard dns I still find this not to be a problemin my situation. As I understand (plz correct me if I'm wrong) the wildcard DNS can cause problems whenever subdomains are actually manually created.

My situation
This technique: wildcard dns/virtual host (server alias) is primarily needed to offer customers an visually appealing login/home url for their homepage. There will never be any subdomains created within this specific domain as this domain is used for homepages only.

And indeed I have to correct myself: you didn't mention the wildcard dns but it was mentioned in the 2nd post.

Conclusion
To have the ServerAlias change made I need to have it done by my hosting company (as idd I found out that through SSH acces was denied in the folder containing httpd.conf).

Thnx for the support and the insight on issues concerning wildcard DNS, I'll be heading back to my hostingcompany first thing in the morning.
 
I have another question which is connected to the same subject so I'll post it here.

Since activating the wildcard virtual host on a reseller level is not a (officialy supported) function by DA, will the manual activation (by modifying httpd.conf) create any problems with current or future versions of DA on a reseller level?.

In other words if an update of DA is installed will the wildcard virtual host still be active (reseller level)?
 
Back
Top