Solved

Adding additional DC's failing...Possibly DNS Issues.

Posted on 2006-11-14
6
1,174 Views
Last Modified: 2007-12-19
I recently migrated an NT DC -> 2003. The master DNS server is still NT4.0. Im having issues adding additional DCs to the network and its apparent there is a DNS issue.

I have created A Names and NS on the master DNS pointing to the 2003 DC's IP address. All have failed.
There is WINS on this network.
NetBIOS is enabled.


##################################
Error when trying to add another DC to network.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain XXX.XXX.XXX:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.XXX.XXX.XXX

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

XXX.XXX.XXX.XXX

- One or more of the following zones do not include delegation to its child zone:

XXX.XXX.XXX
XXX.XXX
XXX
. (the root zone)

For information about correcting this problem, click Help.


##################################
DCDIAG Report

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\NT4
      Starting test: Connectivity
         The host 433ed27c-be45-4eb3-b59f-ac34c2223dc6._msdcs.XXX.XXX.XXX could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name

         (433ed27c-be45-4eb3-b59f-ac34c2223dc6._msdcs.XXX.XXX.XXX)

         couldn't be resolved, the server name (nt4.XXX.XXX.XXX) resolved

         to the IP address (XXX.XXX.XXX.XXX) and was pingable.  Check that the

         IP address is registered correctly with the DNS server.
         ......................... NT4 failed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\NT4
      Skipping all tests, because server NT4 is
      not responding to directory service requests
   
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   
   Running partition tests on : DOMAINNAME
      Starting test: CrossRefValidation
         ......................... DOMAINNAME passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DOMAINNAME passed test CheckSDRefDom
   
   Running enterprise tests on : XXX.XXX.XXX
      Starting test: Intersite
         ......................... XXX.XXX.XXX passed test Intersite
      Starting test: FsmoCheck
         ......................... XXX.XXX.XXX passed test FsmoCheck

###################################
NETDIAG /FIX


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

    Computer Name: NT4
    DNS Host Name: nt4.XXX.XXX.XXX
    System info : Microsoft Windows Server 2003 (Build 3790)
    Processor : x86 Family 15 Model 4 Stepping 8, GenuineIntel
    List of installed hotfixes :
        KB893756
        KB896358
        KB896424
        KB896428
        KB898715
        KB899587
        KB899588
        KB899589
        KB899591
        KB900725
        KB901017
        KB901214
        KB902400
        KB904706
        KB905414
        KB908519
        KB908531
        KB910437
        KB911280
        KB911562
        KB911567
        KB911927
        KB912919
        KB914388
        KB914389
        KB917344
        KB917422
        KB917734
        KB917953
        KB918439
        KB920213
        KB920214
        KB920670
        KB920683
        KB920685
        KB921398
        KB921883
        KB922582
        KB922616
        KB922760
        KB922819
        KB923191
        KB923414
        KB923980
        KB924191
        KB924496
        KB925486
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : nt4
        IP Address . . . . . . . . : XXX.XXX.XXX.31
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : XXX.XXX.XXX.1
        Primary WINS Server. . . . : XXX.XXX.XXX.34
        Dns Servers. . . . . . . . : 127.0.0.1


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed

        WINS service test. . . . . : Passed

        Ipx configration
            Network Number . . . . : 0000b988
            Node . . . . . . . . . : 000c29769f4c
            Frame type . . . . . . : 802.2



    Adapter : IPX Internal Interface

        Netcard queries test . . . : Passed

        Ipx configration
            Network Number . . . . : 00000000
            Node . . . . . . . . . : 000000000001
            Frame type . . . . . . : Ethernet II



    Adapter : IpxLoopbackAdapter

        Netcard queries test . . . : Passed

        Ipx configration
            Network Number . . . . : 0000b988
            Node . . . . . . . . . : 000c29769f4c
            Frame type . . . . . . : 802.2



    Adapter : NDISWANIPX

        Netcard queries test . . . : Passed

        Ipx configration
            Network Number . . . . : 00000000
            Node . . . . . . . . . : ee3420524153
            Frame type . . . . . . : Ethernet II




Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{548BA5F8-4E70-418B-927F-86E4B17521EE}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
    [FATAL] Failed to fix: DC DNS entry XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.pdc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.gc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.1d322d93-79e1-4bbb-865a-ba2ad7928c0c.domains._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry gc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry 433ed27c-be45-4eb3-b59f-ac34c2223dc6._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.dc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.dc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._tcp.Default-First-Site-Name._sites.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _gc._tcp.Default-First-Site-Name._sites.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kerberos._udp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kpasswd._tcp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _kpasswd._udp.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry ForestDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.ForestDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry DomainDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.DomainDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Failed to fix: DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.XXX.XXX.XXX. re-registeration on DNS server '127.0.0.1' failed.
DNS Error code: DNS_ERROR_RCODE_NOT_IMPLEMENTED
    [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for this DC on DNS server '127.0.0.1'.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{548BA5F8-4E70-418B-927F-86E4B17521EE}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{548BA5F8-4E70-418B-927F-86E4B17521EE}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed


Netware configuration
    You are not logged in to your preferred server .
    Netware User Name. . . . . . . :
    Netware Server Name. . . . . . :
    Netware Tree Name. . . . . . . :
    Netware Workstation Context. . :

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

0
Comment
Question by:bigjimbo813
  • 4
  • 2
6 Comments
 
LVL 9

Author Comment

by:bigjimbo813
ID: 17943054
Event Viewer: DNS Server Log


A zone transfer request for the secondary zone xxx.xxx.xxx.in-addr.arpa was refused by the master DNS server at xxx.xxx.xxx.xxx. Check the zone at the master server xxx.xxx.xxx.xxxto verify that zone transfer is enabled to this server.  To do so, use the DNS console, and select master server xxx.xxx.xxx.xxx as the applicable server, then in secondary zone xxx.xxx.xxx.in-addr.arpa Properties, view the settings on the Zone Transfers tab.  Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
0
 
LVL 51

Accepted Solution

by:
Netman66 earned 500 total points
ID: 17943101
You're going to have to use DNS on the 2003 server for AD.  NT4 is not capable of hosting the Service Records required for Active Directory.

This isn't an issue if you want to continue to use the NT4 server, simply forward to that DNS server from the 2003 DNS server.

If you need help setting this up let us know.
0
 
LVL 9

Author Comment

by:bigjimbo813
ID: 17943137
I have all the DNS info on the 2003 server. How would I continue with your suggestion?
0
Control application downtime with dependency maps

Visualize the interdependencies between application components better with Applications Manager's automated application discovery and dependency mapping feature. Resolve performance issues faster by quickly isolating problematic components.

 
LVL 9

Author Comment

by:bigjimbo813
ID: 17943197
i think i have resolved the issue. It always happens when i finally bring my self to actually post a ? vs answer.

Ill post back ina bit
0
 
LVL 51

Expert Comment

by:Netman66
ID: 17943215
Point all servers and clients exclusively to your new DNS server.  Restart the Netlogon Service and run IPCONFIG /registerdns on the console of the server to ge tthe records in place.

0
 
LVL 9

Author Comment

by:bigjimbo813
ID: 17951310
Sorry for the delay, the issue was that the new DNS server was not the primary and the NT4 DNS was. Therefore I made the new 2003 DNS zone all "primary" then ran netdiag /fix which replaced all the missing SRV's. Doing that resolved all the issues.

man what a headache, a migration never caused me this much grief in the past.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preface Having the need * to contact many different companies with different infrastructures * do remote maintenance in their network required us to implement a more flexible routing solution. As RAS, PPTP, L2TP and VPN Client connections are no…
by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Windows 10 is mostly good. However the one thing that annoys me is how many clicks you have to do to dial a VPN connection. You have to go to settings from the start menu, (2 clicks), Network and Internet (1 click), Click VPN (another click) then fi…
Both in life and business – not all partnerships are created equal. As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

14 Experts available now in Live!

Get 1:1 Help Now