01 02

BIND [RESOLVIDO]

13. Re: BIND [RESOLVIDO]

renato_pacheco
(usa Debian)

Enviado em 24/09/2009 - 17:16h

Grilei pá krai! Vc vai renomear todos os seus named.conf pra named.conf.old:

# mv named.conf named.conf.old

E vai fazer um novo named.conf, com esse conteúdo aki:

###################################
named.conf
###################################
options {
directory "/var/named";
auth-nxdomain no;
listen-on-v6 { any; };
};

zone "." IN {
type hint;
file "root.hints";
};

zone "minharede01.com.br" IN {
type master;
file "minharede01.com.br.hosts";
};

zone "0.168.192.in-addr.arpa" IN {
type master;
file "192.168.0.53.rev";
};

Renomeie os seus db's (minharede01.com.br.hosts e 192.168.0.53.rev), como ensinei acima e crie novos db's (inclusive estes aki q colocarei):

######################
root.hints
######################

; <<>> DiG 9.4.2 <<>> @e.root-servers.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37221
;; flags: qr aa rd; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 14
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;. IN NS

;; ANSWER SECTION:
. 518400 IN NS E.ROOT-SERVERS.NET.
. 518400 IN NS J.ROOT-SERVERS.NET.
. 518400 IN NS G.ROOT-SERVERS.NET.
. 518400 IN NS A.ROOT-SERVERS.NET.
. 518400 IN NS F.ROOT-SERVERS.NET.
. 518400 IN NS M.ROOT-SERVERS.NET.
. 518400 IN NS I.ROOT-SERVERS.NET.
. 518400 IN NS D.ROOT-SERVERS.NET.
. 518400 IN NS C.ROOT-SERVERS.NET.
. 518400 IN NS B.ROOT-SERVERS.NET.
. 518400 IN NS H.ROOT-SERVERS.NET.
. 518400 IN NS K.ROOT-SERVERS.NET.
. 518400 IN NS L.ROOT-SERVERS.NET.

;; ADDITIONAL SECTION:
A.ROOT-SERVERS.NET. 3600000 IN A 198.41.0.4
A.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:ba3e::2:30
B.ROOT-SERVERS.NET. 3600000 IN A 192.228.79.201
C.ROOT-SERVERS.NET. 3600000 IN A 192.33.4.12
D.ROOT-SERVERS.NET. 3600000 IN A 128.8.10.90
E.ROOT-SERVERS.NET. 3600000 IN A 192.203.230.10
F.ROOT-SERVERS.NET. 3600000 IN A 192.5.5.241
F.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:2f::f
G.ROOT-SERVERS.NET. 3600000 IN A 192.112.36.4
H.ROOT-SERVERS.NET. 3600000 IN A 128.63.2.53
H.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:500:1::803f:235
I.ROOT-SERVERS.NET. 3600000 IN A 192.36.148.17
J.ROOT-SERVERS.NET. 3600000 IN A 192.58.128.30
J.ROOT-SERVERS.NET. 3600000 IN AAAA 2001:503:c27::2:30

;; Query time: 204 msec
;; SERVER: 192.203.230.10#53(192.203.230.10)
;; WHEN: Fri May 29 20:17:48 2009
;; MSG SIZE rcvd: 500

############################
minharede01.com.br.hosts
############################

$TTL 38400
$ORIGIN minharede01.com.br.
@ IN SOA @ maq03.minharede01.com.br. root.maq03.minharede01.com.br. (
220820091
3H
15M
1W
1D )
@ IN NS maq03.minharede01.com.br.
maq03 IN A 192.168.0.53
www IN CNAME maq03.minharede01.com.br.
ftp IN CNAME maq03.minharede01.com.br.

##################
192.168.0.53.rev
##################

$TTL 38400
@ IN SOA minharede01.com.br. root.maq03.minharede01.com.br. (
220820091
3H
15M
1W
1D )
IN NS maq03.minharede01.com.br.
53 IN PTR maq03.minharede01.com.br.

Depois vc reinicia o serviço.

0 0

Quote

14. Re: BIND [RESOLVIDO]

jfcl10
(usa Conectiva)

Enviado em 25/09/2009 - 11:47h

Descobri o erro do DNS

Por incrivel que pareça estava no Virtualbox, por algum motivo aquela porcaria não deixava o DNS funcionar, agora arranjei um máquina e instalei o CL10 e configurei o BIND pelo Webmind e depois dei uma olhada no código e estava supinpa!!!!!

Ufa depois dessa nunca mais, vou tentar usar o VMWare, mas agradeço a sua ajuda

Valew!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

0 0

Quote

15. BIND OK

jfcl10
(usa Conectiva)

Enviado em 27/09/2009 - 12:20h

Ola galera to postando a resolução do meu problema:

##############
named.conf
##############
options {
directory "/var/named";
dump-file "/var/named/dump/named_dump.db";
statistics-file "/var/named/dump/named.stats";
memstatistics-file "/var/named/dump/named.memstats";
listen-on { any; };
};

zone "." {
type hint;
file "named.ca";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
};

zone "rede01" {
type master;
file "/var/named/rede01.hosts";
};

zone "0.168.192.in-addr.arpa" {
type master;
file "/var/named/192.168.0.rev";
};

##############
rede01.hosts
##############
$ttl 38400
rede01. IN SOA ns1.rede01. root.ns1.rede01 (
1254060789
10800
3600
604800
38400 )
rede01. IN NS ns1.rede01.
ns1.rede01.rede01. IN A 192.168.0.100
intranet.rede01. IN CNAME ns1.rede01.
smtp.rede01. IN MX 20 ns1.rede01
ns1.rede01. IN A 192.168.0.100

##############
192.168.0.rev
##############
$ttl 38400
0.168.192.in-addr.arpa. IN SOA ns1.rede01. root.ns1.rede01 (
1254060966
10800
3600
604800
38400 )
0.168.192.in-addr.arpa. IN NS ns1.rede01.
100.0.168.192.in-addr.arpa. IN PTR ns1.rede01.

------------------------------------------------------

Na linha 6 estava a configuração padrão listen-on { 127.0.0.1/32;}; com isso o Bind dava NXDOMAIN no status e entao mudei para listen-on { any}; e pronto ele funcionou.

No VMWare alem de fazer a mesma configuração tive que mudar o arquivo resolv.conf.

##############
resolv.conf
##############
nameserver 192.168.121.2
nameserver 192.168.0.100 -> inclua esta linha com o endereço IP que você colocou no servidor DNS
search rede01 -> mude de localdomain para o nome do seu dominio.

Agora teste com o dig:
dig apelido.dominio

ex.: dig intranet.rede01

o resultado será:

; <<>> DiG 9.2.3 <<>> intranet.rede01
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54805
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;intranet.rede01. IN A

;; ANSWER SECTION:
intranet.rede01. 38400 IN CNAME ns1.rede01.
ns1.rede01. 38400 IN A 192.168.0.100

;; AUTHORITY SECTION:
rede01. 38400 IN NS ns1.rede01.

;; Query time: 13 msec
;; SERVER: 192.168.0.100#53(192.168.0.100)
;; WHEN: Sun Sep 27 11:29:48 2009
;; MSG SIZE rcvd: 81

0 0

Quote