Virtual Hosts - Dúvidas

[bfbicalho]

Boa noite para todos,

Ando meio afastado do fórum, porém venho desenvolvendo alguns trabalhos...

Venho tentando configurar um servidor web e tudo funcionando tranquilo até o momento. consegui configurar o servidor bind9 e faze-lo funcionar no debian, mas como a linha de comandos dos dois são praticamente os mesmos venho tirar uma dúvida em relação a virtual hosts.

Vendo esse vídeo: http://www.youtube.com/watch?v=X5OEoaYXx5s, consegui fazer o virtual hosts, porém sem conseguir fazer o servidor web funcionar corretamente no apache2.

apliquei o comando cat no log de erros do apache2 e me veio a seguinte informação:

# cat /var/log/apache2/error.log|less
[Wed Nov 13 21:39:27 2013] [notice] Apache/2.2.22 (Debian) configured -- resuming normal operations
[Wed Nov 13 21:39:27 2013] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Nov 13 21:39:27 2013] [notice] Apache/2.2.22 (Debian) configured -- resuming normal operations
[Wed Nov 13 21:39:28 2013] [notice] caught SIGTERM, shutting down
[Wed Nov 13 21:39:29 2013] [notice] Apache/2.2.22 (Debian) mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 configured -- resuming normal operations
[Wed Nov 13 21:39:30 2013] [notice] Graceful restart requested, doing restart
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Nov 13 21:39:30 2013] [notice] Apache/2.2.22 (Debian) mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) configured -- resuming nor
mal operations
[Wed Nov 13 21:40:42 2013] [notice] caught SIGTERM, shutting down
[Wed Nov 13 21:40:52 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Nov 13 21:40:52 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Nov 13 21:40:52 2013] [notice] Digest: done
[Wed Nov 13 21:40:52 2013] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_ssl/2.2.22 OpenS
SL/1.0.1e configured -- resuming normal operations
[Wed Nov 13 21:41:51 2013] [notice] Graceful restart requested, doing restart
[Wed Nov 13 21:41:51 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Nov 13 21:41:51 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Nov 13 21:41:51 2013] [notice] Digest: done
[Wed Nov 13 21:41:51 2013] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_ssl/2.2.22 OpenS
SL/1.0.1e configured -- resuming normal operations
[Wed Nov 13 21:42:02 2013] [notice] Graceful restart requested, doing restart
[Wed Nov 13 21:42:02 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Nov 13 21:42:02 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Nov 13 21:42:02 2013] [notice] Digest: done
[Wed Nov 13 21:42:02 2013] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations
[Wed Nov 13 21:44:04 2013] [notice] Graceful restart requested, doing restart
[Wed Nov 13 21:44:04 2013] [error] (9)Bad file descriptor: apr_socket_accept: (client socket)
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Nov 13 21:44:04 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Nov 13 21:44:04 2013] [notice] Digest: done
[Wed Nov 13 21:44:04 2013] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations
[Wed Nov 13 21:44:29 2013] [error] [client 192.168.1.4] File does not exist: /var/www/favicon.ico
[Wed Nov 13 21:50:13 2013] [notice] caught SIGTERM, shutting down
[Wed Nov 13 21:50:14 2013] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Wed Nov 13 21:50:14 2013] [notice] Digest: generating secret for digest authentication ...
[Wed Nov 13 21:50:14 2013] [notice] Digest: done
[Wed Nov 13 21:50:14 2013] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u5 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_ssl/2.2.22 OpenSSL/1.0.1e configured -- resuming normal operations
[Wed Nov 13 22:06:00 2013] [error] [client 192.168.1.4] File does not exist: /var/www/favicon.ico
[Wed Nov 13 22:06:25 2013] [error] [client 192.168.1.4] SoftException in Application.cpp:564: Directory "/var/www/brunofbicalho" is writeable by group
[Wed Nov 13 22:06:25 2013] [error] [client 192.168.1.4] Premature end of script headers: index.php
[Wed Nov 13 22:07:20 2013] [error] [client 192.168.1.4] SoftException in Application.cpp:564: Directory "/var/www/brunofbicalho" is writeable by group
[Wed Nov 13 22:07:20 2013] [error] [client 192.168.1.4] Premature end of script headers: index.php
[Wed Nov 13 22:07:48 2013] [error] [client 192.168.1.4] SoftException in Application.cpp:564: Directory "/var/www/brunofbicalho" is writeable by group
[Wed Nov 13 22:07:48 2013] [error] [client 192.168.1.4] Premature end of script headers: index.php
[Wed Nov 13 22:21:44 2013] [notice] caught SIGTERM, shutting down

tentei acessar pelo dominio que eu criei para a minha rede interna, porém não aparece nada, muito menos pelo localhost. o domínio criado por mim é: brunofbicalho.com, será que tem algo errado na configuração do meu servidor bind9? apliquei o comando nslookup e resolveu o nome certinho, mas no navegador dá problema.

consegui configurar basicamente dns, apache2, mysql server, phpmyadmin e ftp tudo no ubuntu, porém no momento estou fazendo no debian e tive problemas também do phpmyadmin funcionar normalmente.

Alguém poderia me ajudar?

Obrigado pela ajuda.

EDITANDO...

Eu sem querer editei o arquivo default com as configurações do meu site e com isso apresentou o problema, porém tirei as configurações e o apache voltou a funcionar numa boa... mas ainda sim tenho problemas de redirecionamento. isso eu vi depois de sair uum pouco do ambiente de estudos e distrair a cabeça um pouco.

Obrigado.