Todos os produtos
Search
Central de documentação

Alibaba Cloud DNS:Testar resolução de DNS

Última atualização: Jun 27, 2026

Se não for possível acessar o site ou se um registro DNS não estiver resolvendo corretamente, use os métodos a seguir para verificar o status do nome de domínio e confirmar a efetividade do registro DNS.

Comandos dig e nslookup

As ferramentas de linha de comando mais comuns para consultas DNS incluem o dig, que fornece informações detalhadas de depuração, e o nslookup, disponível por padrão no Windows.

Importante

Como interpretar os resultados: se a saída da consulta DNS corresponder às configurações definidas no Alibaba Cloud DNS, o registro DNS foi propagado.

Caso a saída não corresponda, verifique o TTL. Se o cache local ainda estiver válido, aguarde sua expiração antes de testar novamente.

Se o cache já tiver expirado e os resultados ainda não coincidirem, consulte Solucionar rapidamente problemas de resolução ineficaz.

Comando Dig

1. Consulta básica

Nota

Comando: dig <your_domain_name> (Exemplo: dig example.com)

$ dig example.com
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7585
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;example.com.                   IN      A

;; ANSWER SECTION:
example.com.            10      IN      A       96.7.128.175
example.com.            10      IN      A       96.7.128.198
example.com.            10      IN      A       23.192.228.84
example.com.            10      IN      A       23.215.0.136
example.com.            10      IN      A       23.192.228.80
example.com.            10      IN      A       23.215.0.138

;; Query time: 0 msec
;; WHEN: Tue Feb 18 13:31:55 CST 2025
;; MSG SIZE  rcvd: 125

2. Consulta por tipo de registro

Nota

Comando: dig <your_domain_name> <record_type> (Exemplo: dig example.com NS)

$ dig example.com NS
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com NS
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29146
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;example.com.                   IN      NS

;; ANSWER SECTION:
example.com.            10      IN      NS      b.iana-servers.net.
example.com.            10      IN      NS      a.iana-servers.net.

;; Query time: 0 msec
;; WHEN: Tue Feb 18 15:03:03 CST 2025
;; MSG SIZE  rcvd: 93

O exemplo a seguir mostra a saída quando um registro DNS não foi propagado ou não está configurado (Exemplo: dig example.com cname).

$ dig example.com cname
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com cname
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39890
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;example.com.                   IN      CNAME

;; AUTHORITY SECTION:
example.com.            5       IN      SOA     ns.icann.org. noc.dns.icann.org. 2025011545 7200 3600 1209600 3600

;; Query time: 143 msec
;; WHEN: Tue Feb 18 13:50:18 CST 2025
;; MSG SIZE  rcvd: 94

3. Consultar um servidor DNS específico

Nota

Comando para servidor DNS do Alibaba Cloud: dig <your_domain_name> @ns1.alidns.com (Exemplo: dig example.com @ns1.alidns.com)

Comando para servidor DNS público: dig <your_domain_name> @223.5.5.5 (Exemplo: dig example.com @223.5.5.5)

$ dig example.com @ns1.alidns.com
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com @ns1.alidns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32895
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096

;; QUESTION SECTION:
;example.com.                   IN      A

;; AUTHORITY SECTION:
example.com.            600     IN      SOA     ns1.alidns.com. hostmaster.hichina.com. 2025021713 3600 1200 86400 600

;; Query time: 5 msec
;; WHEN: Tue Feb 18 15:22:09 CST 2025
;; MSG SIZE  rcvd: 112
$ dig example.com @223.5.5.5
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com @223.5.5.5
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42292
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1408

;; QUESTION SECTION:
;example.com.                   IN      A

;; ANSWER SECTION:
example.com.            67      IN      A       96.7.128.175
example.com.            67      IN      A       96.7.128.198
example.com.            67      IN      A       23.215.0.136
example.com.            67      IN      A       23.215.0.138
example.com.            67      IN      A       23.192.228.84
example.com.            67      IN      A       23.192.228.80

;; Query time: 1 msec
;; SERVER: 223.5.5.5#53(223.5.5.5)
;; WHEN: Tue Feb 18 15:16:32 CST 2025
;; MSG SIZE  rcvd: 136

4. Rastrear o caminho de resolução com dig +trace

Nota

Comando: dig <your_domain_name> +trace (Exemplo: dig example.com +trace)

$ dig example.com +trace
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> example.com +trace
;; global options: +cmd
.                       515049  IN      NS      j.root-servers.net.
.                       515049  IN      NS      k.root-servers.net.
.                       515049  IN      NS      a.root-servers.net.
.                       515049  IN      NS      b.root-servers.net.
.                       515049  IN      NS      c.root-servers.net.
.                       515049  IN      NS      d.root-servers.net.
.                       515049  IN      NS      e.root-servers.net.
.                       515049  IN      NS      f.root-servers.net.
.                       515049  IN      NS      g.root-servers.net.
.                       515049  IN      NS      h.root-servers.net.
.                       515049  IN      NS      i.root-servers.net.
.                       515049  IN      NS      l.root-servers.net.
.                       515049  IN      NS      m.root-servers.net.
;; Received 819 bytes from 100.100.2.136#53(100.100.2.136) in 1 ms

com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
;; Received 839 bytes from 198.41.0.4#53(a.root-servers.net) in 2 ms

example.com.            172800  IN      NS      a.iana-servers.net.
example.com.            172800  IN      NS      b.iana-servers.net.
;; Received 326 bytes from 192.26.92.30#53(c.gtld-servers.net) in 2 ms

example.com.            86400   IN      A       96.7.128.175
example.com.            86400   IN      A       96.7.128.198
example.com.            86400   IN      A       23.192.228.84
example.com.            86400   IN      A       23.215.0.136
example.com.            86400   IN      A       23.192.228.80
example.com.            86400   IN      A       23.215.0.138
;; Received 134 bytes from 199.43.135.53#53(a.iana-servers.net) in 143 ms

5. Encontrar o ip de saída público do cliente

Nota

Comando: dig +short TXT whoami.ds.akahelp.net

$ dig +short TXT whoami.ds.akahelp.net
"ns"
"47.xxx.xxx.14"

6. Encontrar os servidores DNS de um domínio

Nota

Comando: dig ns <your_domain_name> (Apenas o nome de domínio raiz é necessário.)

$ dig ns example.com
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> ns example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58283
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;example.com.                   IN      NS

;; ANSWER SECTION:
example.com.            10      IN      NS      a.iana-servers.net.
example.com.            10      IN      NS      b.iana-servers.net.

;; Query time: 5 msec
;; SERVER:
;; WHEN: Tue Feb 18 16:09:33 CST 2025
;; MSG SIZE  rcvd: 93

7. Testar a precisão da resolução inteligente

Nota

Comando: dig @<authoritative_dns_server> <domain_name> +subnet=<client_ip> (Exemplo: dig @ns1.alidns.com example.com +subnet=10.10.10.10)

$ dig @ns1.alidns.com example.com +subnet=10.10.10.10
; <<>> DiG 9.11.36-RedHat-9.11.36-16.0.1.al8 <<>> @ns1.alidns.com example.com +subnet=10.10.10.10
; (9 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60880
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; CLIENT-SUBNET: 10.10.10.10/32/24

;; QUESTION SECTION:
;example.com.                   IN      A

;; AUTHORITY SECTION:
example.com.            600     IN      SOA     ns1.alidns.com. hostmaster.hichina.com. 2024120417 3600 1200 86400 600

;; Query time: 0 msec
;; SERVER:
;; WHEN: Tue Feb 18 16:19:41 CST 2025
;; MSG SIZE  rcvd: 124

Comando Nslookup

1. Verificar os resultados da resolução DNS local.

Nota

Comando: nslookup <your_domain_name> (Exemplo: nslookup example.com)

$ nslookup example.com
Server:         xxx
Address:        xxx#53

Non-authoritative answer:
Name:   example.com
Address: 23.192.228.84
Name:   example.com
Address: 23.215.0.136
Name:   example.com
Address: 23.192.228.80
Name:   example.com
Address: 23.215.0.138
Name:   example.com
Address: 96.7.128.175
Name:   example.com
Address: 96.7.128.198
Name:   example.com
Address: 2600:1408:ec00:36::1736:7f31
Name:   example.com
Address: 2600:1408:ec00:36::1736:7f24
Name:   example.com
Address: 2600:1406:bc00:53::b81e:94ce
Name:   example.com
Address: 2600:1406:bc00:53::b81e:94c8
Name:   example.com
Address: 2600:1406:3a00:21::173e:2e66
Name:   example.com
Address: 2600:1406:3a00:21::173e:2e65

2. Consultar um servidor DNS público

Nota

Comando: nslookup <your_domain_name> <public_dns_server> (Exemplo usando um servidor DNS público do Alibaba Cloud: nslookup example.com 223.5.5.5)

$ nslookup example.com 223.5.5.5
Server:         223.5.5.5
Address:        223.5.5.5#53

Non-authoritative answer:
Name:   example.com
Address: 23.192.228.84
Name:   example.com
Address: 23.215.0.138
Name:   example.com
Address: 23.215.0.136
Name:   example.com
Address: 23.192.228.80
Name:   example.com
Address: 96.7.128.175
Name:   example.com
Address: 96.7.128.198
Name:   example.com
Address: 2600:1406:3a00:21::173e:2e65
Name:   example.com
Address: 2600:1406:bc00:53::b81e:94ce
Name:   example.com
Address: 2600:1408:ec00:36::1736:7f24
Name:   example.com
Address: 2600:1406:3a00:21::173e:2e66
Name:   example.com
Address: 2600:1406:bc00:53::b81e:94c8
Name:   example.com
Address: 2600:1408:ec00:36::1736:7f31

3. Consulta por tipo de registro

Nota

Comando: nslookup -type=<record_type> <your_domain_name> (Exemplo: nslookup -type=NS example.com)

$ nslookup -type=NS example.com
Server:         100.100.2.136
Address:        100.100.2.136#53

Non-authoritative answer:
example.com     nameserver = b.iana-servers.net.
example.com     nameserver = a.iana-servers.net.

Authoritative answers can be found from:

4. Consultar um servidor autoritativo específico

Nota

Comando: nslookup <your_domain_name> <authoritative_server> (Exemplo: nslookup example.com ns1.alidns.com)

$ nslookup example.com ns1.alidns.com
Server:         ns1.alidns.com
Address:        120.76.107.55#53

*** Can't find example.com: No answer