Caio, Poste o arquivo: /etc/bind/db.0.168.192.in-addr.arpa para que possamos verificar.
[]'s Em 05/10/2010, às 06:30, Caio Abreu Ferreira escreveu: > Prezado Valdinei > > Você estava correto, foi somente questão de acrescentar a letra "a" > no arquivo named.conf.local e o reverso voltou a funcionar corretamente. > > Obrigado pela ajuda !! > > Surgiu outro problema :-D. > > Uma forma de testar o arquivo de configuração, não o > named.conf.local, é através do comando named-checkconfig. Quando eu executo o > comando named-checkconfig, tanto no arquivo db.particula.local quanto no > arquivo db.0.168.192.in-addr.arpa, estão aparecendo a mesma mensagem de erro, > texto abaixo. Já fiz várias alterações nos arquivos de configuração > db.particula.local e db.0.168.192.in-addr.arpa, inclusive remover todos os > comentários, mas mesmo assim continua aparecendo as mensagens de erro abaixo. > > ns1:~# named-checkconf /etc/bind/db.particula.local > /etc/bind/db.particula.local:1: syntax error near ';' > ns1:~# named-checkconf /etc/bind/db.0.168.192.in-addr.arpa > /etc/bind/db.0.168.192.in-addr.arpa:1: syntax error near ';' > > Alguma idéia do que pode estar faltando e eu não estou conseguindo > encontrar? > > De novo, obrigado pela ajuda. > > .''`. Caio Abreu Ferreira > : :' : [email protected] > `. `'` Debian User > `- Key fingerprint = 97F8 61AC 605F 8A8B 3BA1 D479 8C9A 52E8 6478 601F > > On (30/09/10 10:00), Valdinei Ferreira de Lima wrote: >> Caio, >> >> >> #### VOCÊ DECLAROU >> zone "79.168.192.in-addr.arp" { >> type master; >> file "/etc/bind/db.79.168.192.in-addr.arpa"; >> }; >> >> >> #### CORRETO >> zone "79.168.192.in-addr.arpa" { >> type master; >> file "/etc/bind/db.79.168.192.in-addr.arpa"; >> }; >> >> >> Faltou um a no addr.arp(aqui) >> >> >> De qualquer forma, depois de fazer a alteração, verifique a saida do [named] >> no log. >> >> >> Em 30/09/2010, às 09:51, caio abreu ferreira escreveu: >> >>> Lista >>> >>> Estou seguindo alguns tutoriais, principalmente os do howto forge, para >>> configurar um >>> servidor de dns que ira responder a um domínio local. A configuração desse >>> servidor de dns é >>> para estudo. Para fazer a configuração fiz o seguinte até agora. >>> >>> ##### Dados técnicos >>> - dns primário - dns1.particula.local - 192.168.79.5 >>> - dns secundário - dns2.particula.local - 192.168.79.6 >>> - GNU Linux Debian Stable >>> >>> ##### cat /etc/bind/named.conf.local >>> zone "particula.local" { >>> type master; >>> file "/etc/bind/db.particula.local"; >>> allow-transfer { 192.168.79.6; }; >>> notify yes; >>> }; >>> >>> zone "79.168.192.in-addr.arp" { >>> type master; >>> file "/etc/bind/db.79.168.192.in-addr.arpa"; >>> }; >>> >>> ##### cat /etc/bind/db.particula.local >>> ; Start of Authority (SOA) record >>> $TTL 900 >>> @ IN SOA ns1.particula.local. root.particula.local. ( >>> 3600; serial >>> 3600; refresh, seconds >>> 3600; retry, seconds >>> 3600; expire, seconds >>> 900 ); minimum, seconds >>> >>> ; Name Server (NS) records. >>> IN NS ns1.particula.local. >>> IN NS ns2.particula.local. >>> >>> ; Mail Exchange (MX) records. >>> IN MX 10 server.particula.local. >>> >>> ; Address (A) records. (real-names of machines) >>> IN A 192.168.79.5 >>> ns1 IN A 192.168.79.5 >>> ns2 IN A 192.168.79.6 >>> server IN A 192.168.79.7 >>> >>> ; Aliases in Canonical Name (CNAME) records... >>> www IN CNAME server >>> ftp IN CNAME server >>> proxy IN CNAME server >>> >>> ##### cat /etc/bind/db.79.168.192.in-addr.arpa >>> ; Start of Authority (SOA) record >>> $TTL 900 >>> @ IN SOA ns1.particula.local. root.particula.local. ( >>> 3600; serial >>> 3600; refresh, seconds >>> 3600; retry, seconds >>> 3600; expire, seconds >>> 900 ); minimum, seconds >>> >>> ; Name Server (NS) records. >>> IN NS ns1.particula.local. >>> IN NS ns2.particula.local. >>> >>> ; Addresses point to canonical names (PTR) for reverse lookups >>> 5 IN PTR ns1.particula.local. >>> 6 IN PTR ns2.particula.local. >>> >>> O comando "dig particula.local" esta funcionando corretamente, vide abaixo. >>> >>> ##### dig particula.local >>> ; <<>> DiG 9.6-ESV-R1 <<>> particula.local >>> ;; global options: +cmd >>> ;; Got answer: >>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37138 >>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2 >>> >>> ;; QUESTION SECTION: >>> ;particula.local. IN A >>> >>> ;; ANSWER SECTION: >>> particula.local. 900 IN A 192.168.79.5 >>> >>> ;; AUTHORITY SECTION: >>> particula.local. 900 IN NS ns2.particula.local. >>> particula.local. 900 IN NS ns1.particula.local. >>> >>> ;; ADDITIONAL SECTION: >>> ns1.particula.local. 900 IN A 192.168.79.5 >>> ns2.particula.local. 900 IN A 192.168.79.6 >>> >>> ;; Query time: 1 msec >>> ;; SERVER: 192.168.79.5#53(192.168.79.5) >>> ;; WHEN: Thu Sep 30 09:48:10 2010 >>> ;; MSG SIZE rcvd: 117 >>> >>> O problema esta sendo em relação ao DNS reverso, comando "dig -x >>> 192.168.79.5" >>> >>> ##### dig -x 192.168.79.5 >>> >>> ; <<>> DiG 9.6-ESV-R1 <<>> -x 192.168.79.5 >>> ;; global options: +cmd >>> ;; Got answer: >>> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4396 >>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 >>> >>> ;; QUESTION SECTION: >>> ;5.79.168.192.in-addr.arpa. IN PTR >>> >>> ;; AUTHORITY SECTION: >>> 168.192.in-addr.arpa. 9501 IN SOA prisoner.iana.org. >>> hostmaster.root- >>> servers.org. 2002040800 1800 900 604800 604800 >>> >>> ;; Query time: 17 msec >>> ;; SERVER: 192.168.79.6#53(192.168.79.6) >>> ;; WHEN: Thu Sep 30 09:49:15 2010 >>> ;; MSG SIZE rcvd: 120 >>> >>> Alguém por acaso saberia me dizer o que eu posso estar fazendo de errado? >>> >>> Obrigado. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
