none
At "Summary of DNS test results" one particular DNS server didn't appeared RRS feed

  • Question

  • Hello guys, 

    I've run in one particular problem:

    Our newly DC (that has DNS roll installed) didn't appeared at the bottom of "dcdiag /test:dns /e" rapport. It's very strange because in the output file I saw this:

    "

    Testing server: US-WIL\INF-WILDC01

          Starting test: Connectivity

             ......................... INF-WILDC01 passed test Connectivity

    "

    and this:

    "

    Starting test: DNS

                                                 .........................

                                                 INF-WILDC01 passed test DNS

    "

    But no information at: 

    "Starting test: DNS

             Test results for domain controllers:

    "

    Regarding that this server is now a successfully promoted DC (passed all tests from here: https://technet.microsoft.com/en-us/library/cc794717%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396) 

    The final text from DC Diag should look like this :

             

    Summary of DNS test results:


                                                Auth Basc Forw Del  Dyn  RReg Ext
                _________________________________________________________________
                Domain: xxxx

                   INF-xxx                  PASS PASS PASS PASS PASS FAIL n/a  

    all our dc/dns appeared but this particular server not.

    In addition I've run  "dcdiag /test:dns /s:inf-wildc01.xxxxx" and the output show like this:

    "

    Directory Server Diagnosis


    Performing initial setup:

       * Identified AD Forest. 
       Done gathering initial info.


    Doing initial required tests


       Testing server: US-WIL\INF-WILDC01

          Starting test: Connectivity

             ......................... INF-WILDC01 passed test Connectivity



    Doing primary tests


       Testing server: US-WIL\INF-WILDC01


          Starting test: DNS



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

             ......................... INF-WILDC01 passed test DNS


       Running partition tests on : DomainDnsZones


       Running partition tests on : ForestDnsZones


       Running partition tests on : Schema


       Running partition tests on : Configuration


       Running partition tests on : xxx

       Running enterprise tests on : xxxx

          Starting test: DNS

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

             controllers:



                DNS server: 2001:500:12::d0d (g.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:500:12::d0d               
                DNS server: 2001:500:1::53 (h.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:500:1::53               
                DNS server: 2001:500:200::b (b.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:500:200::b               
                DNS server: 2001:500:2f::f (f.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:500:2f::f               
                DNS server: 2001:500:9f::42 (l.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:500:9f::42               
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:503:ba3e::2:30               
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:503:c27::2:30               
                DNS server: 2001:7fd::1 (k.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:7fd::1               
                DNS server: 2001:7fe::53 (i.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:7fe::53               
                DNS server: 2001:dc3::35 (m.root-servers.net.)

                   1 test failure on this DNS server

                   PTR record query for the 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 failed on the DNS server 2001:dc3::35               
             ......................... xxx passed test DNS"

                                                 and again no info like this " Summary of DNS test results:


                                                Auth Basc Forw Del  Dyn  RReg Ext
                _________________________________________________________________
                Domain: xxxx

                   INF-xxx                  PASS PASS PASS PASS PASS FAIL n/a  "

    Any ideea ? 

             
    Tuesday, August 8, 2017 7:05 AM

Answers

  • Hi

    The problem was resolved.

    It seems that this server wasn't accessible all the time on LDAP ports.

    Was really difficult to trace, because this behavior manifest aleatory.

    Also, our gateway policy blocked DNS to use external Root Hints.

    • Marked as answer by Ionut Sandu Friday, September 1, 2017 12:34 PM
    Friday, August 18, 2017 1:05 PM

All replies

  • Hi Ionut Sandu

    If possible, could you show me some screenshots of dcdiag /test:dns /e results?

    You could upload the screenshots to onedrive and then provide me the link:

    https://onedrive.live.com/?id=root&cid=69B8CF49D744DC26

    Best Regards,

    Candy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 9, 2017 8:45 AM
  • Hi Ionut Sandu

    Just want to confirm the current situations.

    Please feel free to let us know if you need further assistance.             

    Best Regards,

    Candy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, August 11, 2017 8:31 AM
  • Hi

    The problem was resolved.

    It seems that this server wasn't accessible all the time on LDAP ports.

    Was really difficult to trace, because this behavior manifest aleatory.

    Also, our gateway policy blocked DNS to use external Root Hints.

    • Marked as answer by Ionut Sandu Friday, September 1, 2017 12:34 PM
    Friday, August 18, 2017 1:05 PM
  • Hi Ionut Sandu,

    Thanks for your updating.

    You could mark the useful information as an answer to help other community members find the helpful reply quickly.

    Best Regards,

    Candy


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, August 21, 2017 1:49 AM