httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Bligh <a...@alex.org.uk>
Subject Re: [users@httpd] Should name based virtual hosts work when the ServerName is an IP address?
Date Wed, 30 May 2012 18:59:45 GMT


--On 30 May 2012 14:41:53 +0200 Matus UHLAR - fantomas <uhlar@fantomas.sk> 
wrote:

> I worked around this problem by defining fake name in NameVirtualHost and
> VirtualHost sections
>
># some.na.me maps to 192.168.0.1
> NameVirtualHost some.na.me
> NameVirtualHost 192.168.0.1
>
># some.na.me is not resolvable from outside, so this host will ONLY get #
># default hosts - unspecified below
> <VirtualHost some.na.me>
> ServerName some.na.me
> </VirtualHost>
>
># This host will only process requests for 192.168.0.1
> <VirtualHost 192.168.0.1>
> ServerName 192.168.0.1
> </VirtualHost>

OK, so it is the <VirtualHost some.na.me> that is fixing this (really) not
the ServerName some.na.me line. I'm already doing the latter:
 ServerName default.example.com

My problem is this is an automated install system and (broadly speaking)
I have no control over DNS.

Is there anything else I can do, like (e.g.) put the IP address as
a hex constant or something in <VirtualHost>? Or disable this rather
annoying feature?

-- 
Alex Bligh

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message