Servidor DNS BIND9 com Debian9 não resolve.

1. Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 11/10/2018 - 11:52h

Bom dia,

Instalei o Bind9 no Debian 9, a instalação correu perfeita, porém quando tento resolver nomes na rede, de um pc para outro ele não encontra.

Verifiquei o serviço do Bind9 e reportou o serguinte:


root@horus:/home/systems# service bind9 status
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-10-11 10:45:41 -03; 59min ago
Docs: man:named(8)
Main PID: 512 (named)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/bind9.service
└─512 /usr/sbin/named -f -u bind

out 11 11:32:01 horus named[512]: address not available resolving 'rtdxf.tubemogul.com/A/IN': 2610:a1:1016::68#53
out 11 11:33:11 horus named[512]: address not available resolving 'tiles.r53-2.services.mozilla.com/A/IN': 2600:9000:5303:400::1#53
out 11 11:33:15 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5300:7d00::1#53
out 11 11:34:45 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5303:8900::1#53
out 11 11:34:45 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5306:be00::1#53
out 11 11:36:00 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5305:3100::1#53
out 11 11:36:21 horus named[512]: address not available resolving 'wpad.sc.cloud/A/IN': 2001:dcd:3::10#53
out 11 11:36:21 horus named[512]: address not available resolving 'wpad.sc.cloud/A/IN': 2001:dcd:2::10#53
out 11 11:36:21 horus named[512]: address not available resolving 'cloud/DNSKEY/IN': 2001:dcd:2::10#53
out 11 11:36:31 horus named[512]: client 172.16.99.7#53742 (settings-win.data.microsoft.com): query (cache) 'settings-win.data.microsoft.com/A/IN' denied
root@horus:/home/systems#


Obs.: Fiz testes do pc para o servidor dns e resolveu legal.


  


2. Re: Servidor DNS BIND9 com Debian9 não resolve.

Reginaldo de Matias
saitam

(usa Slackware)

Enviado em 11/10/2018 - 14:36h

Victor Fonseca (viktur2711) escreveu:

Bom dia,

Instalei o Bind9 no Debian 9, a instalação correu perfeita, porém quando tento resolver nomes na rede, de um pc para outro ele não encontra.

Verifiquei o serviço do Bind9 e reportou o serguinte:


root@horus:/home/systems# service bind9 status
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-10-11 10:45:41 -03; 59min ago
Docs: man:named(8)
Main PID: 512 (named)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/bind9.service
└─512 /usr/sbin/named -f -u bind

out 11 11:32:01 horus named[512]: address not available resolving 'rtdxf.tubemogul.com/A/IN': 2610:a1:1016::68#53
out 11 11:33:11 horus named[512]: address not available resolving 'tiles.r53-2.services.mozilla.com/A/IN': 2600:9000:5303:400::1#53
out 11 11:33:15 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5300:7d00::1#53
out 11 11:34:45 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5303:8900::1#53
out 11 11:34:45 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5306:be00::1#53
out 11 11:36:00 horus named[512]: address not available resolving 'ping.chartbeat.net/A/IN': 2600:9000:5305:3100::1#53
out 11 11:36:21 horus named[512]: address not available resolving 'wpad.sc.cloud/A/IN': 2001:dcd:3::10#53
out 11 11:36:21 horus named[512]: address not available resolving 'wpad.sc.cloud/A/IN': 2001:dcd:2::10#53
out 11 11:36:21 horus named[512]: address not available resolving 'cloud/DNSKEY/IN': 2001:dcd:2::10#53
out 11 11:36:31 horus named[512]: client 172.16.99.7#53742 (settings-win.data.microsoft.com): query (cache) 'settings-win.data.microsoft.com/A/IN' denied
root@horus:/home/systems#


Obs.: Fiz testes do pc para o servidor dns e resolveu legal.


como estão os arquivos de configuração named.conf e os de zonas direta/reversa?
Poste aqui para analisarmos



http://mundodacomputacaointegral.blogspot.com.br/
Twitter: http://twitter.com/@blogcomputacao
Facebook: http://www.facebook.com/BlogComputacao
Grupo Linux no Telegram: https://goo.gl/KQYqhN
Grupo Linguagens de Programação no Telegram: https://goo.gl/7sJF95
Grupo FreeBSD no Telegram: https://goo.gl/mzp7XT
Grupo Infra TI Corporate no Telegram: https://t.me/InfraTICorporate
Grupo CodeIgniter no Telegram: https://t.me/CodeIgniterBrasil
Blog: http://goo.gl/Cuixk
Coleção de Howtos Linux e FreeBSD https://goo.gl/UHDVtK
Canal do Blog: https://t.me/blogcomputacao




3. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 11/10/2018 - 16:31h

Obrigado pelo retorno!

named.conf.local
  GNU nano 2.7.4                                                      Arquivo: /etc/bind/named.conf.local

//
// Do any local configuration here
//

zone "ac.cloud" {
type master;
file "/etc/bind/db.ac.cloud";
};

zone "61.136.162.in-addr.arpa" {
type master;
file "/etc/bind/db.61.136.162";
};

// Consider adding the 1918 zones here, if they are not used in your
// organization
// include "/etc/bind/zones.rfc1918";

  GNU nano 2.7.4                                                        Arquivo: /etc/bind/db.ac.cloud

;
; BIND zone file for ac.cloud
;

$TTL 3D
@ IN SOA horus.ac.cloud. root.ac.cloud. (
2010111101 ; serial
8H ; refresh
2H ; retry
4W ; expire
1D ) ; minimum
;
NS ns ; Inet address of name server

ns A 162.136.61.182
ac.cloud. A 162.136.61.182
horus A 162.136.61.182
router A 162.136.61.250 ; router ADSL
gateway CNAME router
gw CNAME router

  GNU nano 2.7.4                                                       Arquivo: /etc/bind/db.61.136.162

;
; BIND zone file for 162.136.61.xxx
;

$TTL 3D
@ IN SOA horus.ac.cloud. root.ac.cloud. (
2010111101 ; serial
8H ; refresh
2H ; retry
4W ; expire
1D ) ; minimum
;
NS ns.ac.cloud. ; Nameserver address

182 PTR horus.ac.cloud.
182 PTR ns.ac.cloud.
250 PTR router.ac.cloud.



4. Re: Servidor DNS BIND9 com Debian9 não resolve.

Reginaldo de Matias
saitam

(usa Slackware)

Enviado em 11/10/2018 - 17:07h

Victor Fonseca (viktur2711) escreveu:

Obrigado pelo retorno!

named.conf.local
  GNU nano 2.7.4                                                      Arquivo: /etc/bind/named.conf.local

//
// Do any local configuration here
//

zone "ac.cloud" {
type master;
file "/etc/bind/db.ac.cloud";
};

zone "61.136.162.in-addr.arpa" {
type master;
file "/etc/bind/db.61.136.162";
};

// Consider adding the 1918 zones here, if they are not used in your
// organization
// include "/etc/bind/zones.rfc1918";

  GNU nano 2.7.4                                                        Arquivo: /etc/bind/db.ac.cloud

;
; BIND zone file for ac.cloud
;

$TTL 3D
@ IN SOA horus.ac.cloud. root.ac.cloud. (
2010111101 ; serial
8H ; refresh
2H ; retry
4W ; expire
1D ) ; minimum
;
NS ns ; Inet address of name server

ns A 162.136.61.182
ac.cloud. A 162.136.61.182
horus A 162.136.61.182
router A 162.136.61.250 ; router ADSL
gateway CNAME router
gw CNAME router

  GNU nano 2.7.4                                                       Arquivo: /etc/bind/db.61.136.162

;
; BIND zone file for 162.136.61.xxx
;

$TTL 3D
@ IN SOA horus.ac.cloud. root.ac.cloud. (
2010111101 ; serial
8H ; refresh
2H ; retry
4W ; expire
1D ) ; minimum
;
NS ns.ac.cloud. ; Nameserver address

182 PTR horus.ac.cloud.
182 PTR ns.ac.cloud.
250 PTR router.ac.cloud.


o serial a cada atualização nos arquivos de zonas direta e reversa deve ser atualizado também, atualmente foi observado que está assim
2010111101      ; serial


corresponde ANOMESDIAID

Outra no servidor DNS em /etc/resolv.conf colocou o domain e nameserver o IP do servidor?

Os testes nslookup no domínio e IP?

Nas máquinas clientes, colocou o IP do servidor DNS como resolvedor de nomes ?



http://mundodacomputacaointegral.blogspot.com.br/
Twitter: http://twitter.com/@blogcomputacao
Facebook: http://www.facebook.com/BlogComputacao
Grupo Linux no Telegram: https://goo.gl/KQYqhN
Grupo Linguagens de Programação no Telegram: https://goo.gl/7sJF95
Grupo FreeBSD no Telegram: https://goo.gl/mzp7XT
Grupo Infra TI Corporate no Telegram: https://t.me/InfraTICorporate
Grupo CodeIgniter no Telegram: https://t.me/CodeIgniterBrasil
Blog: http://goo.gl/Cuixk
Coleção de Howtos Linux e FreeBSD https://goo.gl/UHDVtK
Canal do Blog: https://t.me/blogcomputacao




5. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 11/10/2018 - 17:25h

Devo alterar algo no serial?
Quanto ao dns: apontei sim.

Segue resolv.conf:
root@horus:/home/systems# nano /etc/resolv.conf
GNU nano 2.7.4 Arquivo: /etc/resolv.conf

domain ac.cloud
search ac.cloud
nameserver 127.0.0.1

nslookup

root@horus:/home/systems# nslookup 162.136.61.182
Server: 127.0.0.1
Address: 127.0.0.1#53

182.61.136.162.in-addr.arpa name = ns.ac.cloud.
182.61.136.162.in-addr.arpa name = horus.ac.cloud.


root@horus:/home/systems# nslookup 61.136.162
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find 61.136.162: NXDOMAIN


root@horus:/home/systems# nslookup horus.ac.cloud
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: horus.ac.cloud
Address: 162.136.61.182

named-checkzone

root@horus:/home/systems# named-checkzone 61.136.162.in-addr.arpa /etc/bind/db.61.136.162
zone 61.136.162.in-addr.arpa/IN: loaded serial 2010111101
OK



6. Re: Servidor DNS BIND9 com Debian9 não resolve.

Reginaldo de Matias
saitam

(usa Slackware)

Enviado em 11/10/2018 - 17:27h

Victor Fonseca (viktur2711) escreveu:

Devo alterar algo no serial?
Quanto ao dns: apontei sim.

Segue resolv.conf:
root@horus:/home/systems# nano /etc/resolv.conf
GNU nano 2.7.4 Arquivo: /etc/resolv.conf

domain ac.cloud
search ac.cloud
nameserver 127.0.0.1

nslookup

root@horus:/home/systems# nslookup 162.136.61.182
Server: 127.0.0.1
Address: 127.0.0.1#53

182.61.136.162.in-addr.arpa name = ns.ac.cloud.
182.61.136.162.in-addr.arpa name = horus.ac.cloud.


root@horus:/home/systems# nslookup 61.136.162
Server: 127.0.0.1
Address: 127.0.0.1#53

** server can't find 61.136.162: NXDOMAIN

named-checkzone

root@horus:/home/systems# named-checkzone 61.136.162.in-addr.arpa /etc/bind/db.61.136.162
zone 61.136.162.in-addr.arpa/IN: loaded serial 2010111101
OK


O seu reverse está com problema, conforme o erro apresentado "** server can't find 61.136.162: NXDOMAIN"
troque nameserver 127.0.0.1 pelo IP do servidor DNS e execute o nslookup para o domínio e IP.
Também altere o serial conforme a data de alteração no padrão ANOMESDIAID
Ex: 2018101101

http://mundodacomputacaointegral.blogspot.com.br/
Twitter: http://twitter.com/@blogcomputacao
Facebook: http://www.facebook.com/BlogComputacao
Grupo Linux no Telegram: https://goo.gl/KQYqhN
Grupo Linguagens de Programação no Telegram: https://goo.gl/7sJF95
Grupo FreeBSD no Telegram: https://goo.gl/mzp7XT
Grupo Infra TI Corporate no Telegram: https://t.me/InfraTICorporate
Grupo CodeIgniter no Telegram: https://t.me/CodeIgniterBrasil
Blog: http://goo.gl/Cuixk
Coleção de Howtos Linux e FreeBSD https://goo.gl/UHDVtK
Canal do Blog: https://t.me/blogcomputacao




7. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 11/10/2018 - 17:39h

Feito, seguem os retornos:
root@horus:/home/systems# nslookup ac.cloud
Server: 162.136.61.182
Address: 162.136.61.182#53

Name: ac.cloud
Address: 162.136.61.182

root@horus:/home/systems# nslookup 162.136.61.182
Server: 162.136.61.182
Address: 162.136.61.182#53

182.61.136.162.in-addr.arpa name = horus.ac.cloud.
182.61.136.162.in-addr.arpa name = ns.ac.cloud.

Também retorno do status do bind9
root@horus:/home/systems# service bind9 status
● bind9.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-10-11 17:36:23 -03; 1min 58s ago
Docs: man:named(8)
Process: 805 ExecStop=/usr/sbin/rndc stop (code=exited, status=0/SUCCESS)
Main PID: 833 (named)
Tasks: 7 (limit: 4915)
CGroup: /system.slice/bind9.service
└─833 /usr/sbin/named -f -u bind

out 11 17:37:23 horus named[833]: address not available resolving 'ns-1470.awsdns-55.org/A/IN': 2600:9000:5304:3a00::1#53
out 11 17:37:23 horus named[833]: address not available resolving 'ns-1470.awsdns-55.org/AAAA/IN': 2600:9000:5304:3a00::1#53
out 11 17:37:23 horus named[833]: address not available resolving 'gtm08.nexac.com/A/IN': 2001:500:90:1::5#53
out 11 17:37:23 horus named[833]: address not available resolving 'ocsp.comodoca.com/A/IN': 2a02:1788:0:200::5bd1:c404#53
out 11 17:37:24 horus named[833]: address not available resolving 'a652.dscb.akamai.net/A/IN': 2600:1480:1::c1#53
out 11 17:37:24 horus named[833]: address not available resolving 'jp/DNSKEY/IN': 2a01:8840:1ba::25#53
out 11 17:37:24 horus named[833]: address not available resolving 'g.dns.jp/AAAA/IN': 2001:dc2::2#53
out 11 17:37:24 horus named[833]: address not available resolving 'g.dns.jp/AAAA/IN': 2001:2f8:0:100::163#53
out 11 17:37:24 horus named[833]: address not available resolving 'g.dns.jp/AAAA/IN': 2001:240::54#53
out 11 17:38:03 horus named[833]: address not available resolving 'vivaolinux.com.br/DS/IN': 2001:12f8:c::10#53



8. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 11/10/2018 - 17:50h

Estranho que o reverse continua com o erro:
root@horus:/home/systems# nslookup 61.136.162
Server: 162.136.61.182
Address: 162.136.61.182#53

** server can't find 61.136.162: NXDOMAIN



9. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 15/10/2018 - 10:30h

viktur2711 escreveu:

Estranho que o reverse continua com o erro:
root@horus:/home/systems# nslookup 61.136.162
Server: 162.136.61.182
Address: 162.136.61.182#53

** server can't find 61.136.162: NXDOMAIN


Bom dia, alguem sabe me dizer qual o motivo de ainda estar reportando esse erro?
** server can't find 61.136.162: NXDOMAIN

Estou rodando alguns foruns, mas não consigo chegar na solução.




10. Re: Servidor DNS BIND9 com Debian9 não resolve.

Reginaldo de Matias
saitam

(usa Slackware)

Enviado em 15/10/2018 - 10:44h

Victor Fonseca (viktur2711) escreveu:

viktur2711 escreveu:

Estranho que o reverse continua com o erro:
root@horus:/home/systems# nslookup 61.136.162
Server: 162.136.61.182
Address: 162.136.61.182#53

** server can't find 61.136.162: NXDOMAIN


Bom dia, alguem sabe me dizer qual o motivo de ainda estar reportando esse erro?
** server can't find 61.136.162: NXDOMAIN

Estou rodando alguns foruns, mas não consigo chegar na solução.



testou nslookup domain.com e nskookup IP ?

tem algum firewall bloqueando porta 53 no UDP/TCP?

http://mundodacomputacaointegral.blogspot.com.br/
Twitter: http://twitter.com/@blogcomputacao
Facebook: http://www.facebook.com/BlogComputacao
Grupo Linux no Telegram: https://goo.gl/KQYqhN
Grupo Linguagens de Programação no Telegram: https://goo.gl/7sJF95
Grupo FreeBSD no Telegram: https://goo.gl/mzp7XT
Grupo Infra TI Corporate no Telegram: https://t.me/InfraTICorporate
Grupo CodeIgniter no Telegram: https://t.me/CodeIgniterBrasil
Blog: http://goo.gl/Cuixk
Coleção de Howtos Linux e FreeBSD https://goo.gl/UHDVtK
Canal do Blog: https://t.me/blogcomputacao




11. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 15/10/2018 - 11:02h

Testei sim, aparentemente esta ok.
root@horus:/home/systems# nslookup ac.cloud
Server: 162.136.61.182
Address: 162.136.61.182#53

Name: ac.cloud
Address: 162.136.61.182

root@horus:/home/systems# nslookup 162.136.61.182
Server: 162.136.61.182
Address: 162.136.61.182#53

182.61.136.162.in-addr.arpa name = ns.ac.cloud.
182.61.136.162.in-addr.arpa name = horus.ac.cloud.

porém não consigo resolver nomes na rede e ainda aparece o erro no reverso:
root@horus:/home/systems# nslookup 61.136.162
Server: 162.136.61.182
Address: 162.136.61.182#53

** server can't find 61.136.162: NXDOMAIN


Quanto ao firewall, não tenho nenhum.


12. Re: Servidor DNS BIND9 com Debian9 não resolve.

Victor Fonseca
viktur2711

(usa openSUSE)

Enviado em 15/10/2018 - 11:17h

root@horus:/home/systems# nslookup 182.61.136.162
Server: 162.136.61.182
Address: 162.136.61.182#53

** server can't find 162.136.61.182.in-addr.arpa: SERVFAIL




01 02



Patrocínio

Site hospedado pelo provedor HostGator.
Linux banner
Linux banner
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts