Bug#606317: apache2: upgrade to sysvinit causes apache virtualhosts to fail - started before bind9

[Thomas Goirand <zigo@debian.org>]

On 01/06/2011 08:17 AM, christoph@hilbert.alphasky.net wrote:
> Thomas Goirand <zigo@debian.org> wrote:
> 
>> Hi Ian,
>>
>> I think that if nobody found the issue, it's because nowadays, almost
>> everyone is using IP based virtualhosts, because starting apache with
>> named virtualhost makes apache resolve as many hostname as you have
>> vhosts, and in many situations, this can take a long long time.
>>
>> Anyway, did you try to add a:
>>
>> Sound-Start: bind9
>>
>> in the init script dependencies of Apache? Does it fixes the issue?
>>
>> Thomas
>>
>>
>>
> 
> Hi Thomas,
> most people who have a restricted number of ip addresses use name based virtualhosts though.

This has absolutely nothing to do with the number of IP address you may
have. You can for example do:

<VirtualHost 1.2.3.4:80>
	ServerName www.example.com
	DocumentRoot [...]
	[...]
</VirtualHost>
<VirtualHost 1.2.3.5:80>
	ServerName www.example.org
	DocumentRoot [...]
	[...]
</VirtualHost>

This way, you'd have both www.example.com and www.example.org sharing
the same IP.

> I rather think that not everyone is running bind in order to ensure name resolving. External
> nameservers are another option and I don't know wheter it can be considered as a default to
> have an own one.

Whether you use external or embedded name server has nothing to do with
it: resolving is slow, and you should avoid it.

Anyway, that's just my 2 cents of advice, and it has nothing to do with
this bug entry anymore... :)

Thomas