Re: Bind sobe e não resolve
Cara, desculpe novamente, mas logo no início do arquivo é $ORIGIN. e não
@ORIGIN.
É só trocar a @ pelo $
Abraço,
Fabrício Lamonica
-----Original Message-----
From: Harlei Liguori Marcelino <hliguori@gmail.com>
To: Fabrício Lamonica <lista@linux.netenet.com.br>
Cc: Helio Loureiro <helio@loureiro.eng.br>, debianlista
<debian-user-portuguese@lists.debian.org>
Subject: Re: Bind sobe e não resolve
Date: Mon, 8 Aug 2011 13:34:18 -0300
Olá amigo, nada :(
o arquivo ficou assim:
@ORIGIN.
$TTL 604800
@ IN SOA brasilia.meudominio.com. root.meudominio.com. (
3 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
$ORIGIN meudominio.com.
@ IN NS brasilia.meudominio.com.
brasilia IN A 192.168.0.5
fortaleza IN A 192.168.0.118
e o resultado:
Aug 8 13:33:12 brasilia named[29960]: starting BIND 9.7.3 -u bind
Aug 8 13:33:12 brasilia named[29960]: 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=' 'CPPFLAGS='
Aug 8 13:33:12 brasilia named[29960]: adjusted limit on open files from
1024 to 1048576
Aug 8 13:33:12 brasilia named[29960]: found 2 CPUs, using 2 worker
threads
Aug 8 13:33:12 brasilia named[29960]: using up to 4096 sockets
Aug 8 13:33:12 brasilia named[29960]: loading configuration from
'/etc/bind/named.conf'
Aug 8 13:33:12 brasilia named[29960]: reading built-in trusted keys
from file '/etc/bind/bind.keys'
Aug 8 13:33:12 brasilia named[29960]: using default UDP/IPv4 port
range: [1024, 65535]
Aug 8 13:33:12 brasilia named[29960]: using default UDP/IPv6 port
range: [1024, 65535]
Aug 8 13:33:12 brasilia named[29960]: listening on IPv6 interfaces,
port 53
Aug 8 13:33:12 brasilia named[29960]: listening on IPv4 interface lo,
127.0.0.1#53
Aug 8 13:33:12 brasilia named[29960]: listening on IPv4 interface eth1,
10.1.1.2#53
Aug 8 13:33:12 brasilia named[29960]: listening on IPv4 interface eth0,
192.168.0.5#53
Aug 8 13:33:12 brasilia named[29960]: listening on IPv4 interface eth2,
187.37.1.37#53
Aug 8 13:33:12 brasilia named[29960]: generating session key for
dynamic DNS
Aug 8 13:33:12 brasilia named[29960]: set up managed keys zone for view
_default, file 'managed-keys.bind'
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
254.169.IN-ADDR.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
2.0.192.IN-ADDR.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
100.51.198.IN-ADDR.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
113.0.203.IN-ADDR.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
255.255.255.255.IN-ADDR.ARPA
Aug 8 13:33:12 brasilia named[29960]: 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
Aug 8 13:33:12 brasilia named[29960]: 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
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
D.F.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
8.E.F.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
9.E.F.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
A.E.F.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
B.E.F.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: automatic empty zone:
8.B.D.0.1.0.0.2.IP6.ARPA
Aug 8 13:33:12 brasilia named[29960]: command channel listening on
127.0.0.1#953
Aug 8 13:33:12 brasilia named[29960]: command channel listening
on ::1#953
Aug 8 13:33:12 brasilia named[29960]: zone 0.in-addr.arpa/IN: loaded
serial 1
Aug 8 13:33:12 brasilia named[29960]: zone 127.in-addr.arpa/IN: loaded
serial 1
Aug 8 13:33:12 brasilia named[29960]: zone 0.168.192.in-addr.arpa/IN:
loaded serial 2
Aug 8 13:33:12 brasilia named[29960]: zone 255.in-addr.arpa/IN: loaded
serial 1
Aug 8 13:33:12 brasilia named[29960]: /etc/bind/db.meudominio.com:1:
ignoring out-of-zone data (\@ORIGIN)
Aug 8 13:33:12 brasilia named[29960]:
dns_master_load: /etc/bind/db.meudominio.com:2: unexpected end of line
Aug 8 13:33:12 brasilia named[29960]:
dns_master_load: /etc/bind/db.meudominio.com:1: unexpected end of input
Aug 8 13:33:12 brasilia named[29960]: zone meudominio.com/IN: loading
from master file /etc/bind/db.meudominio.com failed: unexpected end of
input
Aug 8 13:33:12 brasilia named[29960]: zone meudominio.com/IN: not
loaded due to errors.
Aug 8 13:33:12 brasilia named[29960]: zone localhost/IN: loaded serial
2
Aug 8 13:33:12 brasilia named[29960]: managed-keys-zone ./IN: loading
from master file managed-keys.bind failed: file not found
Aug 8 13:33:12 brasilia named[29960]: managed-keys-zone ./IN: loaded
serial 0
Aug 8 13:33:12 brasilia named[29960]: running
pelo log consegue descobrir mais alguma coisa? não entendo nada de log
de dns :(
att
Harlei
Em 8 de agosto de 2011 13:28, Fabrício Lamonica
<lista@linux.netenet.com.br> escreveu:
Oi, Harlei
Vamos tentar o seguinte:
1. Adicionar as 2 linhas abaixo logo no topo do arquivo:
$ORIGIN .
$TTL 604800
2. Onde eu te sugeri colocar $ORIGIN seudominio. é para
substituir a
palavra seudominio pelo seu domínio em uso. Me expressei mal.
3. Pode tirar a arroba antes de brasilia e fortaleza. Passei
errado para
você.
Com isso, seu arquivo ficaria mais ou menos assim:
@ORIGIN.
$TTL 604800
@ IN SOA brasilia.meudominio.com. root.meudominio.com. (
3 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
$ORIGIN meudominio.com.
@ IN NS brasilia.meudominio.com.
brasilia IN A 192.168.0.5
fortaleza IN A 192.168.0.118
Tenta aí para ver
-----Original Message-----
From: Harlei Liguori Marcelino <hliguori@gmail.com>
To: Fabrício Lamonica <lista@linux.netenet.com.br>
Cc: Helio Loureiro <helio@loureiro.eng.br>, debianlista
<debian-user-portuguese@lists.debian.org>
Subject: Re: Bind sobe e não resolve
Date: Mon, 8 Aug 2011 13:20:50 -0300
Olá meu amigo, obrigado por tentar ajuda...
Ficou assim o arquivo:
;
$TTL 604800
@ IN SOA brasilia.meudominio.com. root.meudominio.com. (
3 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
$ORIGIN seudominio.
@ IN NS brasilia.meudominio.com.
@brasilia IN A 192.168.0.5
@fortaleza IN A 192.168.0.118
e o resultado foi:
Aug 8 13:18:52 brasilia named[29924]: starting BIND 9.7.3 -u
bind
Aug 8 13:18:52 brasilia named[29924]: 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='
'CPPFLAGS='
Aug 8 13:18:52 brasilia named[29924]: adjusted limit on open
files from
1024 to 1048576
Aug 8 13:18:52 brasilia named[29924]: found 2 CPUs, using 2
worker
threads
Aug 8 13:18:52 brasilia named[29924]: using up to 4096 sockets
Aug 8 13:18:52 brasilia named[29924]: loading configuration
from
'/etc/bind/named.conf'
Aug 8 13:18:52 brasilia named[29924]: reading built-in trusted
keys
from file '/etc/bind/bind.keys'
Aug 8 13:18:52 brasilia named[29924]: using default UDP/IPv4
port
range: [1024, 65535]
Aug 8 13:18:52 brasilia named[29924]: using default UDP/IPv6
port
range: [1024, 65535]
Aug 8 13:18:52 brasilia named[29924]: listening on IPv6
interfaces,
port 53
Aug 8 13:18:52 brasilia named[29924]: listening on IPv4
interface lo,
127.0.0.1#53
Aug 8 13:18:52 brasilia named[29924]: listening on IPv4
interface eth1,
10.1.1.2#53
Aug 8 13:18:52 brasilia named[29924]: listening on IPv4
interface eth0,
192.168.0.5#53
Aug 8 13:18:52 brasilia named[29924]: listening on IPv4
interface eth2,
187.37.1.37#53
Aug 8 13:18:52 brasilia named[29924]: generating session key
for
dynamic DNS
Aug 8 13:18:52 brasilia named[29924]: set up managed keys zone
for view
_default, file 'managed-keys.bind'
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
254.169.IN-ADDR.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
2.0.192.IN-ADDR.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
100.51.198.IN-ADDR.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
113.0.203.IN-ADDR.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
255.255.255.255.IN-ADDR.ARPA
Aug 8 13:18:52 brasilia named[29924]: 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
Aug 8 13:18:52 brasilia named[29924]: 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
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
D.F.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
8.E.F.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
9.E.F.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
A.E.F.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
B.E.F.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: automatic empty zone:
8.B.D.0.1.0.0.2.IP6.ARPA
Aug 8 13:18:52 brasilia named[29924]: command channel listening
on
127.0.0.1#953
Aug 8 13:18:52 brasilia named[29924]: command channel listening
on ::1#953
Aug 8 13:18:52 brasilia named[29924]: zone 0.in-addr.arpa/IN:
loaded
serial 1
Aug 8 13:18:52 brasilia named[29924]: zone 127.in-addr.arpa/IN:
loaded
serial 1
Aug 8 13:18:52 brasilia named[29924]: zone
0.168.192.in-addr.arpa/IN:
loaded serial 2
Aug 8 13:18:52 brasilia named[29924]: zone 255.in-addr.arpa/IN:
loaded
serial 1
Aug 8 13:18:52 brasilia
named[29924]: /etc/bind/db.meudominio.com:13:
ignoring out-of-zone data (seudominio)
Aug 8 13:18:52 brasilia
named[29924]: /etc/bind/db.meudominio.com:15:
ignoring out-of-zone data (\@brasilia\194\160\194\160\194\160
\194\160
\194\160\194\160.seudominio)
Aug 8 13:18:52 brasilia
named[29924]: /etc/bind/db.meudominio.com:15:
unknown RR type 'IN '
Aug 8 13:18:52 brasilia named[29924]: zone meudominio.com/IN:
loading
from master file /etc/bind/db.meudominio.com failed: unknown
class/type
Aug 8 13:18:52 brasilia named[29924]: zone meudominio.com/IN:
not
loaded due to errors.
Aug 8 13:18:52 brasilia named[29924]: zone localhost/IN: loaded
serial
2
Aug 8 13:18:52 brasilia named[29924]: managed-keys-zone ./IN:
loading
from master file managed-keys.bind failed: file not found
Aug 8 13:18:52 brasilia named[29924]: managed-keys-zone ./IN:
loaded
serial 0
Aug 8 13:18:52 brasilia named[29924]: running
não parece ter mudado muito :(
posa não faço nem ideia oq mudar mais… maldito arquivo
temperamental :)
att
Harlei
Em 8 de agosto de 2011 12:47, Fabrício Lamonica
<lista@linux.netenet.com.br> escreveu:
Harlei,
não sei como está seu arquivo, mas tenta o seguinte:
1. Na linha anterior ao primeira linha que possua as
entradas de
hosts,
NS ou MX (provavelmente linha 12), insira o seguinte, sem
as
aspas:
"$ORIGIN seudominio." --> não esqueça do ponto no final
2. Nas linhas que possuem as entradas (as que possuem
IN),
adicione uma
arroba logo no início de cada uma delas.
Testa aí e depois posta o resultado.
Abraço,
Fabrício Lamonica
-----Original Message-----
From: Harlei Liguori Marcelino <hliguori@gmail.com>
To: Fabrício Lamonica <lista@linux.netenet.com.br>
Cc: Helio Loureiro <helio@loureiro.eng.br>, debianlista
<debian-user-portuguese@lists.debian.org>
Subject: Re: Bind sobe e não resolve
Date: Mon, 8 Aug 2011 11:59:59 -0300
Realmente da um erro na linha 13 que é onde eu digo quais
são os
hosts... veja abaixo:
Aug 8 11:54:46 brasilia named[29827]: starting BIND
9.7.3 -u
bind
Aug 8 11:54:46 brasilia named[29827]: 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='
'CPPFLAGS='
Aug 8 11:54:46 brasilia named[29827]: adjusted limit on
open
files from
1024 to 1048576
Aug 8 11:54:46 brasilia named[29827]: found 2 CPUs,
using 2
worker
threads
Aug 8 11:54:46 brasilia named[29827]: using up to 4096
sockets
Aug 8 11:54:46 brasilia named[29827]: loading
configuration
from
'/etc/bind/named.conf'
Aug 8 11:54:46 brasilia named[29827]: reading built-in
trusted
keys
from file '/etc/bind/bind.keys'
Aug 8 11:54:46 brasilia named[29827]: using default
UDP/IPv4
port
range: [1024, 65535]
Aug 8 11:54:46 brasilia named[29827]: using default
UDP/IPv6
port
range: [1024, 65535]
Aug 8 11:54:46 brasilia named[29827]: listening on IPv6
interfaces,
port 53
Aug 8 11:54:46 brasilia named[29827]: listening on IPv4
interface lo,
127.0.0.1#53
Aug 8 11:54:46 brasilia named[29827]: listening on IPv4
interface eth1,
10.1.1.2#53
Aug 8 11:54:46 brasilia named[29827]: listening on IPv4
interface eth0,
192.168.0.5#53
Aug 8 11:54:46 brasilia named[29827]: listening on IPv4
interface eth2,
187.37.1.37#53
Aug 8 11:54:46 brasilia named[29827]: generating session
key
for
dynamic DNS
Aug 8 11:54:46 brasilia named[29827]: set up managed
keys zone
for view
_default, file 'managed-keys.bind'
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
254.169.IN-ADDR.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
2.0.192.IN-ADDR.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
100.51.198.IN-ADDR.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
113.0.203.IN-ADDR.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
255.255.255.255.IN-ADDR.ARPA
Aug 8 11:54:46 brasilia named[29827]: 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
Aug 8 11:54:46 brasilia named[29827]: 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
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
D.F.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
8.E.F.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
9.E.F.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
A.E.F.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
B.E.F.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: automatic empty
zone:
8.B.D.0.1.0.0.2.IP6.ARPA
Aug 8 11:54:46 brasilia named[29827]: command channel
listening
on
127.0.0.1#953
Aug 8 11:54:46 brasilia named[29827]: command channel
listening
on ::1#953
Aug 8 11:54:46 brasilia named[29827]: zone
0.in-addr.arpa/IN:
loaded
serial 1
Aug 8 11:54:46 brasilia named[29827]: zone
127.in-addr.arpa/IN:
loaded
serial 1
Aug 8 11:54:46 brasilia named[29827]: zone
0.168.192.in-addr.arpa/IN:
loaded serial 2
Aug 8 11:54:46 brasilia named[29827]: zone
255.in-addr.arpa/IN:
loaded
serial 1
Aug 8 11:54:46 brasilia
named[29827]: /etc/bind/db.meudominio.com:13:
unknown RR type 'IN '
Aug 8 11:54:46 brasilia named[29827]: zone
meudominio.com/IN:
loading
from master file /etc/bind/db.meudominio.com failed:
unknown
class/type
Aug 8 11:54:46 brasilia named[29827]: zone
meudominio.com/IN:
not
loaded due to errors.
Aug 8 11:54:46 brasilia named[29827]: zone localhost/IN:
loaded
serial
2
Aug 8 11:54:46 brasilia named[29827]:
managed-keys-zone ./IN:
loading
from master file managed-keys.bind failed: file not found
Aug 8 11:54:46 brasilia named[29827]:
managed-keys-zone ./IN:
loaded
serial 0
Aug 8 11:54:46 brasilia named[29827]: running
Aug 8 11:54:47 brasilia named[29827]: error (network
unreachable)
resolving 'news.google.com/AAAA/IN': 2001:503:b
só não sei como resolver... parece tudo certinho :(
att
Harlei
Em 8 de agosto de 2011 11:49, Fabrício Lamonica
<lista@linux.netenet.com.br> escreveu:
Harlei,
o que pode ter acontecido é o Bind subir, mas a
zona
estar com
problema
em sua configuração. Assim, ela não é considerada.
Sugiro
dar
uma olhada
no /var/log/daemon.log e restartar o serviço para
ver as
mensagens. Se
for isso, aparecerá uma linha de erro da zona.
Abraço,
Fabrício Lamonica
-----Original Message-----
From: Harlei Liguori Marcelino
<hliguori@gmail.com>
To: Helio Loureiro <helio@loureiro.eng.br>
Cc: debianlista
<debian-user-portuguese@lists.debian.org>
Subject: Re: Bind sobe e não resolve
Date: Mon, 8 Aug 2011 11:43:39 -0300
O DNS subiu sim... ele sobe mas nao resolve
nada...
mudei o 1 pra 2 e nada, continua nao resolvendo...
nao
havia
mudado o
numero pq tava com a configuração inicial, mas
mesmo com
2 nao
funciona :( não resolve nadinha... cruel...
pior q nao sei oq tentar... parece estar tudo
funcionando... mas
é como
se ele não resolvesse nada...
executei de um cliente o comando abaixo, veja:
maquina:~ ozof041$ nslookup
brasilia.meudominio.com
;; Got SERVFAIL reply from 192.168.0.5, trying
next
server
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
*** Can't find brasilia.meudominio.com: No answer
maquina:~ ozof041$
como pode ver ele vai ate o servidor DNS interno e
como
nao tem
resposta
procura o externo... ele realmente nao resolve...
nao sei
pq...
será q
há uma forma de vocês me ajudarem? :(
agradeço desde já
att
Harlei
Em 6 de agosto de 2011 07:58, Helio Loureiro
<helio@loureiro.eng.br>
escreveu:
root@brasilia:/etc/bind# cat
db.meudominio.com
;
$TTL 604800
@ IN SOA
brasilia.meudominio.com.
root.meudominio.com. (
1 ;
Serial
604800 ;
Refresh
86400 ;
Retry
2419200 ;
Expire
604800 ) ;
Negative
Cache TTL
;
@ IN NS
brasilia.meudominio.com.
Como o DNS nem subiu, dê uma olhada no
"/var/log/daemon.log"
para tentar descobrir o que está errado.
Aparentemente todas as entradas estão
certas.
A propósito, vc está atualizando o serial a
cada
mudança? Tente
trocar para 2 e veja se carrega os mapas de
domínio.
[]´s
Helio Loureiro
http://helio.loureiro.eng.br
http://hloureiro.multiply.com
http://twitter.com/helioloureiro
http://gplus.to/helioloureiro
Reply to: