[Resolvido] Problemas configuração Bind e Apache

[rvgugisch]

Bem, fiz os comandos para mudar as permissões e o dono do diretório.

Só não entendi o que eu tenho que colocar e em qual dos arquivos!

Poderia me explicar?

[zekkerj]

Vc tem que criar um registro "A" no arquivo da zona "iparana.gov.br", criando o nome "servidorlinux".

[rvgugisch]

Não está respondendo ainda!

zekkerj , desculpa cara, mas sou iniciante nesse lance de DNS e squid!

Meu arquivo db.iparana.org.br ficou assim:

Código: [Selecionar]

$TTL 604800
@       IN      SOA     serverlinux.iparana.org.br.     root.iparana.org.br. (
        2011021801      ; serial
        3H              ; refresh
        15M             ; retry
        1W              ; expire
        1D)             ; Negative cache TTL

        NS serverlinux.iparana.org.br.
        IN MX 10 serverlinux.iparana.org.br.

serverlinux     A       187.7.131.36
iparana.org.br  A       187.7.131.36
www             A       187.7.131.36
ftp             A       187.7.131.36
smtp            A       187.7.131.36

Código: [Selecionar]

root@serverlinux:/etc/bind# service bind9 restart
 * Stopping domain name service... bind9                                           [ OK ]
 * Starting domain name service... bind9                                           [ OK ]

root@serverlinux:/etc/bind# grep named /var/log/syslog | tail -n 50
Feb 18 13:20:47 serverlinux named[17314]: error (network unreachable) resolving 'dns4.easydns.info/A/IN': 2001:dc3::35#53
Feb 18 13:20:47 serverlinux named[17314]: error (network unreachable) resolving 'dns4.easydns.info/AAAA/IN': 2001:dc3::35#53
Feb 18 13:20:47 serverlinux named[17314]: error (network unreachable) resolving 'dns4.easydns.info/AAAA/IN': 2001:500:1b::1#53
Feb 18 13:20:47 serverlinux named[17314]: error (network unreachable) resolving 'dns4.easydns.info/AAAA/IN': 2001:500:1c::1#53
Feb 18 13:20:48 serverlinux named[17314]: error (network unreachable) resolving 'www.canonical.com/AAAA/IN': 2001:503:a83e::2:30#53
Feb 18 13:20:48 serverlinux named[17314]: error (network unreachable) resolving 'www.canonical.com/AAAA/IN': 2001:503:231d::2:30#53
Feb 18 13:23:08 serverlinux named[17314]: received control channel command 'stop -p'
Feb 18 13:23:08 serverlinux named[17314]: shutting down: flushing changes
Feb 18 13:23:08 serverlinux named[17314]: stopping command channel on 127.0.0.1#953
Feb 18 13:23:08 serverlinux named[17314]: stopping command channel on ::1#953
Feb 18 13:23:08 serverlinux named[17314]: no longer listening on 127.0.0.1#53
Feb 18 13:23:08 serverlinux named[17314]: no longer listening on 10.1.1.1#53
Feb 18 13:23:08 serverlinux named[17314]: no longer listening on 187.7.131.36#53
Feb 18 13:23:08 serverlinux named[17314]: exiting
Feb 18 13:23:09 serverlinux named[17390]: starting BIND 9.7.1-P2 -u bind
Feb 18 13:23:09 serverlinux named[17390]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var' '--enable-threads' '--enable-largefile' '--with-libtool' '--enable-shared' '--enable-static' '--with-openssl=/usr' '--with-gssapi=/usr' '--with-gnu-ld' '--with-dlz-postgres=no' '--with-dlz-mysql=no' '--with-dlz-bdb=yes' '--with-dlz-filesystem=yes' '--with-dlz-ldap=yes' '--with-dlz-stub=yes' '--with-geoip=/usr' '--enable-ipv6' 'CFLAGS=-fno-strict-aliasing -DDIG_SIGCHASE -O2' 'LDFLAGS=-Wl,-Bsymbolic-functions' 'CPPFLAGS='
Feb 18 13:23:09 serverlinux named[17390]: adjusted limit on open files from 1024 to 1048576
Feb 18 13:23:09 serverlinux named[17390]: found 2 CPUs, using 2 worker threads
Feb 18 13:23:09 serverlinux named[17390]: using up to 4096 sockets
Feb 18 13:23:09 serverlinux named[17390]: loading configuration from '/etc/bind/named.conf'
Feb 18 13:23:09 serverlinux named[17390]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Feb 18 13:23:09 serverlinux named[17390]: using default UDP/IPv4 port range: [1024, 65535]
Feb 18 13:23:09 serverlinux named[17390]: using default UDP/IPv6 port range: [1024, 65535]
Feb 18 13:23:09 serverlinux named[17390]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 18 13:23:09 serverlinux named[17390]: listening on IPv4 interface eth1, 10.1.1.1#53
Feb 18 13:23:09 serverlinux named[17390]: listening on IPv4 interface eth0, 187.7.131.36#53
Feb 18 13:23:09 serverlinux named[17390]: generating session key for dynamic DNS
Feb 18 13:23:09 serverlinux named[17390]: set up managed keys zone for view _default, file 'managed-keys.bind'
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 0.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 127.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 254.169.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: D.F.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 8.E.F.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 9.E.F.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: A.E.F.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: B.E.F.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: automatic empty zone: 0.1.1.0.0.2.IP6.ARPA
Feb 18 13:23:09 serverlinux named[17390]: command channel listening on 127.0.0.1#953
Feb 18 13:23:09 serverlinux named[17390]: command channel listening on ::1#953
Feb 18 13:23:09 serverlinux named[17390]: the working directory is not writable
Feb 18 13:23:09 serverlinux named[17390]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Feb 18 13:23:09 serverlinux named[17390]: managed-keys-zone ./IN: loaded serial 0
Feb 18 13:23:10 serverlinux named[17390]: running


[rvgugisch]

Cá estamos novamente.

Bom dia a todos!

[zekkerj]

Confirme que há uma instrução no arquivo "/etc/bind/named.conf" para carregar (include) o arquivo "/etc/bind/named.conf.local".

[rvgugisch]

Sim, está sendo chamado mesmo!

arquivo named.conf

Código: [Selecionar]

//include "/etc/bind/named.conf.options";
//include "/etc/bind/named.conf.local";
//include "/etc/bind/named.conf.default-zones";

[zekkerj]

Esses "//" do início da linha: foi vc que os colocou?

[Master_]

ta comentado rs.

[zekkerj]

Então descomenta essas linhas e testa de novo.

[rvgugisch]

Desculpa pessoal, tava tão desesperado aqui que nem vi que estavam comentadas!

Descomentei, restartei o serviço e aparentemente está funcionando!

Poderiam confirmar?

[zekkerj]

Aqui não tive resposta ainda.

[rvgugisch]

Aqui se digito:

dig iparana.com.br @187.7.131.36 me dá a seguinte resposta:

Código: [Selecionar]

roberto@serverlinux:/etc/bind$ dig iparana.org.br @187.7.131.36

; <<>> DiG 9.7.1-P2 <<>> iparana.org.br @187.7.131.36
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 607
;; flags: qr a rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;iparana.org.br. IN A

;; AUTHORITY SECTION:
iparana.org.br. 86400 IN SOA serverlinux.iparana.org.br. root.iparana.org.br. 2011021801 10800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 187.7.131.36#53(187.7.131.36)
;; WHEN: Mon Feb 21 10:16:52 2011
;; MSG SIZE  rcvd: 85

Está certo isso não???

[zekkerj]

Bate com as informações que vc definiu, não? Mas não tive resposta daqui. Talvez vc precise verificar seu firewall.

[rvgugisch]

O que preciso ver no firewall?

Uma vez postei o lance da porta 53.

É isso novamente?

[zekkerj]

O firewall tem que estar permitindo o recebimento (INPUT) de pacotes vindos de qualquer lugar, na porta 53/udp.

Não lembro se vc chegou a postar informação de firewall.