none
Problemas DNS RRS feed

  • Pergunta

  • Estou com problema no meu DNS, executei o commando dcdiad /teste:dns e retornou a seguinte mensagem:  oque faço?


    C:\Program Files\Support Tools>dcdiag /test:dns

    Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests

       Testing server: Default-First-Site-Name\BRASIL
          Starting test: Connectivity
             ......................... BRASIL passed test Connectivity

    Doing primary tests

       Testing server: Default-First-Site-Name\BRASIL

    DNS Tests are running and not hung. Please wait a few minutes...

       Running partition tests on : ForestDnsZones

       Running partition tests on : DomainDnsZones

       Running partition tests on : Schema

       Running partition tests on : Configuration

       Running partition tests on : symnetics

       Running enterprise tests on : symnetics.dns
          Starting test: DNS
             Test results for domain controllers:

                DC: brasil.symnetics.dns
                Domain: symnetics.dns


                   TEST: Forwarders/Root hints (Forw)
                      Error: Root hints list has invalid root hint server: a.root-se
    rvers.net. (198.41.0.4)
                      Error: Root hints list has invalid root hint server: b.root-se
    rvers.net. (192.228.79.201)
                      Error: Root hints list has invalid root hint server: c.root-se
    rvers.net. (192.33.4.12)
                      Error: Root hints list has invalid root hint server: d.root-se
    rvers.net. (128.8.10.90)
                      Error: Root hints list has invalid root hint server: e.root-se
    rvers.net. (192.203.230.10)
                      Error: Root hints list has invalid root hint server: f.root-se
    rvers.net. (192.5.5.241)
                      Error: Root hints list has invalid root hint server: g.root-se
    rvers.net. (192.112.36.4)
                      Error: Root hints list has invalid root hint server: h.root-se
    rvers.net. (128.63.2.53)
                      Error: Root hints list has invalid root hint server: i.root-se
    rvers.net. (192.36.148.17)
                      Error: Root hints list has invalid root hint server: j.root-se
    rvers.net. (192.58.128.30)
                      Error: Root hints list has invalid root hint server: k.root-se
    rvers.net. (193.0.14.129)
                      Error: Root hints list has invalid root hint server: l.root-se
    rvers.net. (199.7.83.42)
                      Error: Root hints list has invalid root hint server: m.root-se
    rvers.net. (202.12.27.33)

                   TEST: Dynamic update (Dyn)
                      Warning: Dynamic update is enabled on the zone but not secure
    symnetics.dns.

             Summary of test results for DNS servers used by the above domain contro
    llers:

                DNS server: 128.63.2.53 (h.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 128.63.2.53

                DNS server: 128.8.10.90 (d.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 128.8.10.90

                DNS server: 192.112.36.4 (g.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.112.36.4

                DNS server: 192.203.230.10 (e.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.203.230.10

                DNS server: 192.228.79.201 (b.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.228.79.201

                DNS server: 192.33.4.12 (c.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.33.4.12

                DNS server: 192.36.148.17 (i.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.36.148.17

                DNS server: 192.5.5.241 (f.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.5.5.241

                DNS server: 192.58.128.30 (j.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 192.58.128.30

                DNS server: 193.0.14.129 (k.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 193.0.14.129

                DNS server: 198.41.0.4 (a.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 198.41.0.4

                DNS server: 199.7.83.42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 199.7.83.42

                DNS server: 202.12.27.33 (m.root-servers.net.)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.12
    7.in-addr.arpa. failed on the DNS server 202.12.27.33

             Summary of DNS test results:

                                                Auth Basc Forw Del  Dyn  RReg Ext
                   ________________________________________________________________
                Domain: symnetics.dns
                   brasil                       PASS PASS FAIL PASS WARN PASS n/a

             ......................... symnetics.dns failed test DNS

    C:\Program Files\Support Tools>

    quarta-feira, 10 de fevereiro de 2010 14:02

Respostas

  • Poderia verificar:

    1-como o seu servidor possui 2 Nics, configurar no Lan_1 o gateway como o Lan_2 (192.168.7.1) pois para validar o rootHints o servidor procura o acesso a internet, e pode estar utilizando o Lan_1 que não esta com o gtw configurado. Acho dificil ser isso, mas não custa tentar.

    2 - outro teste seria vc substituir o arquivo root hints (%systemroot%\system32\dns\cache.dns) pelo atual que pode ser baixado no site "http://www.internic.net/zones/named.root", salve o arquivo atual "cache.dns" como "cache.dns.old" e baixe o arquivo da internet no diretório citado com o nome "cache.dns".

    3 - verifique nas propriedades do DNS na aba "Root Hints" se esta aparecendo os names servers e o IP normalmente.

    abs

    fsoato
    • Marcado como Resposta Richard Juhasz quarta-feira, 17 de fevereiro de 2010 13:31
    quinta-feira, 11 de fevereiro de 2010 01:26

Todas as Respostas

  • Verifique a configuraçao da NIC, pode ser que tenha algo errado, se fizer algum alteraçao efetue o procedimento abaixo:

    STOP DNS
    START DNS
    ipconfig /flushdns

    STOP NETLogon service
    Start Netlogon

    ipconfig /registerdns

    Abraço,
    Erick Albuquerque | Winsec.Org | PortalTecnologia.net
    quarta-feira, 10 de fevereiro de 2010 14:18
    Moderador
  • Verifique a configuraçao da NIC, pode ser que tenha algo errado, se fizer algum alteraçao efetue o procedimento abaixo:

    STOP DNS
    START DNS
    ipconfig /flushdns

    STOP NETLogon service
    Start Netlogon

    ipconfig /registerdns

    Abraço,
    Erick Albuquerque | Winsec.Org | PortalTecnologia.net

    A configuração da minha NIC é a seguinte: (aparentemente vejo o problema não está ai)

    C:\Program Files\Support Tools>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : brasil
       Primary Dns Suffix  . . . . . . . : symnetics.dns
       Node Type . . . . . . . . . . . . : Unknown
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : Yes
       DNS Suffix Search List. . . . . . : symnetics.dns

    Ethernet adapter Lan_2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
       Physical Address. . . . . . . . . : 00-04-23-AB-D1-D9
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.7.11
       Subnet Mask . . . . . . . . . . . : 255.255.252.0
       Default Gateway . . . . . . . . . : 192.168.7.1
       DNS Servers . . . . . . . . . . . : 192.168.7.11
                                           192.168.7.10
       Primary WINS Server . . . . . . . : 192.168.7.11
       Secondary WINS Server . . . . . . : 192.168.7.10

    Ethernet adapter Lan_1:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8169 Gigabit Ethernet Adapter
       Physical Address. . . . . . . . . : 00-0C-76-B6-01-CA
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.7.10
       Subnet Mask . . . . . . . . . . . : 255.255.252.0
       Default Gateway . . . . . . . . . :
       DNS Servers . . . . . . . . . . . : 192.168.7.10
                                           192.168.7.11
       Primary WINS Server . . . . . . . : 192.168.7.11
       Secondary WINS Server . . . . . . : 192.168.7.10

    C:\Program Files\Support Tools>

    quarta-feira, 10 de fevereiro de 2010 15:37
  • Poderia verificar:

    1-como o seu servidor possui 2 Nics, configurar no Lan_1 o gateway como o Lan_2 (192.168.7.1) pois para validar o rootHints o servidor procura o acesso a internet, e pode estar utilizando o Lan_1 que não esta com o gtw configurado. Acho dificil ser isso, mas não custa tentar.

    2 - outro teste seria vc substituir o arquivo root hints (%systemroot%\system32\dns\cache.dns) pelo atual que pode ser baixado no site "http://www.internic.net/zones/named.root", salve o arquivo atual "cache.dns" como "cache.dns.old" e baixe o arquivo da internet no diretório citado com o nome "cache.dns".

    3 - verifique nas propriedades do DNS na aba "Root Hints" se esta aparecendo os names servers e o IP normalmente.

    abs

    fsoato
    • Marcado como Resposta Richard Juhasz quarta-feira, 17 de fevereiro de 2010 13:31
    quinta-feira, 11 de fevereiro de 2010 01:26
  • Valeu pela ajuda,

    Fiz o procedimento e foi efetuada a atualização do Root Hints.

    Abçs

    Fernando
    quinta-feira, 18 de fevereiro de 2010 23:00