Quoting /usr/share/doc/apache2/NEWS.Debian.gz on my Ubuntu machine:
apache2 (2.4.1-1) unstable; urgency=low
...
Moreover, the configuration mechanism in Debian has changed. All
configurations in sites-enabled and conf-enabled need a ".conf" suffix now.
...
Note this means all existing sites are ignored until they get a ".conf"
suffix and are re-enabled by the use of a2ensite. The script in [3] can
automate that for simple cases. This change also includes Debian default
sites, so the default site has been renamed to 000-default to avoid naming
confusions.
BTW a2ensite accepts the site name without the .conf suffix, I checked.
My experiments on Ubuntu 12.04 (with Apache 2.2, still using the older conventions) show that a2dissite 000-default tries to disable the site called default and finds it's already disabled. So it might work for all the users. I haven't actually tried it out in a fresh Vagrant VM to see if it would successfully disable the default site, because Vagrant is annoying today.
Quoting /usr/share/doc/apache2/NEWS.Debian.gz on my Ubuntu machine:
BTW
a2ensiteaccepts the site name without the .conf suffix, I checked.My experiments on Ubuntu 12.04 (with Apache 2.2, still using the older conventions) show that
a2dissite 000-defaulttries to disable the site calleddefaultand finds it's already disabled. So it might work for all the users. I haven't actually tried it out in a fresh Vagrant VM to see if it would successfully disable the default site, because Vagrant is annoying today.