Always define a ServerName, AFAIK *.example.com would not be valid in 2.2 either, even if it let you define it without error, ServerName should always have a valid resolvable name, at least from the client that will query it.
Note that if you have several virtualhosts ServerName is important so httpd will know exactly to which virtualhost it must deliver each request. In your case since you want to match all subdomains, just add a name of one of your main subdomains for ServerName directive. eg: ServerName main.example.com 2016-09-13 11:36 GMT+02:00 Hajo Locke <hajo.lo...@gmx.de>: > Hello List, > > in apache 2.2 we had a typical vhost like this to realize > wildcardsubdomains: > > <VirtualHost *:80> > ServerName *.example.com > ServerAlias *.example.com > DocumentRoot /var/www/wildcardexample/public_html > </VirtualHost> > > In apache 2.4 wildcards are not allowed in servername. Is it ok to just > comment out servername and run this vhost only with "ServerAlias *. > example.com"? > It seems that servername is not a mandatory directive, apache 2.4 is > starting without problems. > Or is there an better way to realize? > > Thanks, > Hajo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > > -- *Daniel Ferradal* IT Specialist email dferradal at gmail.com linkedin es.linkedin.com/in/danielferradal
