On 06/23/2018 10:34 AM, billy noah wrote:
Thanks Eric, the rdns almost certainly /did /change so that could be the
culprit. Do you have a definitive answer or a way to determine how
apache decides what "ServerName" should be when the directive is
absent?
From the documentation:
If no
Thanks Eric, the rdns almost certainly *did *change so that could be the
culprit. Do you have a definitive answer or a way to determine how apache
decides what "ServerName" should be when the directive is absent? I'll
stick with the policy of using something (even nonsense as you suggested)
in th
On Sat, Jun 23, 2018 at 11:22 AM billy noah wrote:
>
> I am in the process of migrating some sites from a server running Apache
> 2.4.7 to a new installation (Ubuntu 18) running Apache 2.4.29 and running
> into some issues with VirtualHost matching.
>
> On my old server I have a config like this
I am in the process of migrating some sites from a server running Apache
2.4.7 to a new installation (Ubuntu 18) running Apache 2.4.29 and running
into some issues with VirtualHost matching.
On my old server I have a config like this:
ServerAlias *.dev.example.com
VirtualDocumentRoot /va
