none
DNS lookup failing between two domain controllers

    Question

  • First my environment -

    main DC running server 2012R2, set as domaina.net

    second dc running server 08R2, set as domainb.net which is a second domain in the same forest as domaina.net

    now for my issue: when trying to install exchange 2007 w/ SP3 on domainb it fails to find the domain controller it is being installed on

    troubleshooting already done (why I put this here will now be evident):

    added appropriate line to lmhosts file

    ran dcdiag and only fail was due to printers picked up with the RDP session on my laptop

    switched to RDP on my iPad and ran dcdiag /test:dns on both DCs - passed on 2012R2 but failed on 08R2 stating DNS records for the domain are not on the 2012R2 dc

    added domain in dns console but issue and fail continue

    fix the dns issue and the exchange issue should go away (and yes I know that 2007 hits end of life in april 2017)

    any help on this will be greatly appreciated

    Saturday, March 25, 2017 9:24 AM

Answers

  • I did not resolve it as deployed however I di resolve it by redeploying slightly differently.

    Rather than keeping each domain on it's own DC, I put them on the same DC and updated DNS accordingly.  I used separate member servers for each Exchange box and got my redirects working.  Issue resolved.

    Help was greatly appreciated.

    • Marked as answer by Mr. Ganz Monday, August 21, 2017 4:48 AM
    Monday, August 21, 2017 4:47 AM

All replies

  • Hi,
    According to your description, what comes into my mind is to check if all ports between DCs are opened, and check if the second DC is pointed to main DC as DNS.
    You could post us the detail error of dcdiag /test:dns for helping to troubleshoot, and you could also refer to the following article regarding to analysis errors in dcdiag /test:dns and have a try it: https://social.technet.microsoft.com/wiki/contents/articles/17741.dcdiag-for-dns-test-details-explained.aspx
    Best regards,
    Wendy

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

    Monday, March 27, 2017 6:36 AM
    Moderator
  • as per your request, here is the output from dcdiag /test:dns on the DC that fails.  Note -- the actual domain names are listed in the output as are P addresses (internal) and I am fine with that.

    C:\Windows\system32>dcdiag /test:dns
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = v2k3server
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\V2K3SERVER
          Starting test: Connectivity
             The host a73bd966-4832-452f-bf4c-c4534b14d28e._msdcs.virtunetops.net
             could not be resolved to an IP address. Check the DNS server, DHCP,
             server name, etc.
             Got error while checking LDAP and RPC connectivity. Please check your
             firewall settings.
             ......................... V2K3SERVER failed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\V2K3SERVER
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
             ......................... V2K3SERVER passed test DNS
       Running partition tests on : virtual2k3
       Running partition tests on : ForestDnsZones
       Running partition tests on : Schema
       Running partition tests on : Configuration
       Running enterprise tests on : virtunetops.net
          Starting test: DNS
             Test results for domain controllers:
                DC: v2k3server.virtual2k3.net
                Domain: virtual2k3.net

                   TEST: Basic (Basc)
                      Error: No LDAP connectivity
                      Warning: Adapter 00:0D:3A:14:28:50 has dynamic IP address
                      (can be a misconfiguration)
                      No host records (A or AAAA) were found for this DC
                   TEST: Dynamic update (Dyn)
                      Warning: Failed to add the test record dcdiag-test-record in z
    one virtual2k3.net
                   TEST: Records registration (RReg)
                      Network Adapter [00000007] Microsoft Hyper-V Network Adapter:
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _ldap._tcp.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kerberos._tcp.dc._msdcs.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _ldap._tcp.dc._msdcs.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kerberos._tcp.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kerberos._udp.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kpasswd._tcp.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _ldap._tcp.Default-First-Site-Name._sites.virtual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.vir
    tual2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.virtual
    2k3.net
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _kerberos._tcp.Default-First-Site-Name._sites.virtual2k3.ne
    t
                         Error:
                         Missing SRV record at DNS server 10.0.1.4:
                         _ldap._tcp.pdc._msdcs.virtual2k3.net
                   Error: Record registrations cannot be found for all the network
                   adapters
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                _________________________________________________________________
                Domain: virtual2k3.net
                   v2k3server                   PASS FAIL PASS PASS WARN FAIL n/a
             ......................... virtunetops.net failed test DNS

    C:\Windows\system32>

    will look into which ports need to be open for LDAP connectivity

    Tuesday, March 28, 2017 6:31 AM
  • Hi,

    I am checking how the issue is going, if you still have any questions, please feel free to contact us.

    And if the replies as above are helpful, we would appreciate you to mark them as answers, and if you resolve it using your own solution, please share your experience and solution here. It will be greatly helpful to others who have the same question.

    Appreciate for your feedback.

    Best regards,

    Wendy


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

    Thursday, March 30, 2017 8:57 AM
    Moderator
  • I did not resolve it as deployed however I di resolve it by redeploying slightly differently.

    Rather than keeping each domain on it's own DC, I put them on the same DC and updated DNS accordingly.  I used separate member servers for each Exchange box and got my redirects working.  Issue resolved.

    Help was greatly appreciated.

    • Marked as answer by Mr. Ganz Monday, August 21, 2017 4:48 AM
    Monday, August 21, 2017 4:47 AM