Announcement

Collapse
No announcement yet.

Post NT4 / 2003 Upgrade DNS issue

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Post NT4 / 2003 Upgrade DNS issue

    We just upgraded our NT4 domain (mydomain.com) to 2003 AD - everything appeared to go well until we tried dcpromo a new 2003 server as a DC - looked into our DNS and noticed no SRV records - We have a sister domain (otherdomain.com) where we can add a DC - no sweat and there are SRV records in the DNS. For giggles I took the new server and created DNS for a new forest (mydomain.local) no problem - the SRV records are created perfectly - can some come to my emotional rescue and tell me how to get DNS to play nicely with mydomain.com and allow me to bring in a new DC?


    Domain Controller Diagnosis

    Performing initial setup:
    * Verifying that the local machine bupsrv, is a DC.
    * Connecting to directory service on server bupsrv.
    * Collecting site info.
    * Identifying all servers.
    * Identifying all NC cross-refs.
    * Found 1 DC(s). Testing 1 of them.
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\BUPSRV
    Starting test: Connectivity
    * Active Directory LDAP Services Check
    The host 4afba439-5f4b-42d2-8f1d-8a3ad42b342a._msdcs.mydomain.com could not be resolved to an
    IP address. Check the DNS server, DHCP, server name, etc
    Although the Guid DNS name
    (4afba439-5f4b-42d2-8f1d-8a3ad42b342a._msdcs.mydomain.com) couldn't be
    resolved, the server name (bupsrv.mydomain.com) resolved to the IP
    address (192.168.0.10) and was pingable. Check that the IP address is
    registered correctly with the DNS server.
    ......................... BUPSRV failed test Connectivity

    Doing primary tests

    DC: bupsrv.mydomain.com
    Domain: mydomain.com


    TEST: Authentication (Auth)
    Authentication test: Successfully completed

    TEST: Basic (Basc)
    Error: No LDAP connectivity
    Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported
    NETLOGON service is running
    kdc service is running
    DNSCACHE service is running
    DNS service is running
    DC is a DNS server
    Network adapters information:
    Adapter [00000002] 3Com 3C900TPO-based Ethernet Adapter (Generic):
    MAC address is 00:60:08:3B:64:AF
    IP address is static
    IP address: 192.168.0.10
    DNS servers:
    Warning: 192.168.0.11 (<name unavailable>) [Invalid]
    Warning: 192.168.0.10 (<name unavailable>) [Invalid]
    Warning: 192.168.0.9 (<name unavailable>) [Invalid (unreachable)]
    Error: all DNS servers are invalid
    The A record for this DC was found
    The SOA record for the Active Directory zone was found
    The Active Directory zone on this DC/DNS server was found (primary)
    Root zone on this DC/DNS server was not found

    TEST: Forwarders/Root hints (Forw)
    Recursion is enabled
    Forwarders Information:
    209.244.0.3 (<name unavailable>) [Invalid]
    209.244.0.4 (<name unavailable>) [Invalid]

    TEST: Delegations (Del)
    No delegations were found in this zone on this DNS server

    TEST: Dynamic update (Dyn)
    Warning: Dynamic update is enabled on the zone but not secure mydomain.com.
    Test record _dcdiag_test_record added successfully in zone mydomain.com.
    Test record _dcdiag_test_record deleted successfully in zone mydomain.com.

    TEST: Records registration (RReg)
    Error: Record registrations cannot be found for all the network adapters

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

    DNS server: 192.168.0.10 (<name unavailable>)
    1 test failure on this DNS server
    This is a valid DNS server.
    Name resolution is not functional. _ldap._tcp.mydomain.com. failed on the DNS server 192.168.0.10
    [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    DNS server: 192.168.0.11 (<name unavailable>)
    1 test failure on this DNS server
    This is a valid DNS server.
    Name resolution is not functional. _ldap._tcp.mydomain.com. failed on the DNS server 192.168.0.11
    [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    DNS server: 192.168.0.9 (<name unavailable>)
    1 test failure on this DNS server
    This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.0.9
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
    Name resolution is not functional. _ldap._tcp.mydomain.com. failed on the DNS server 192.168.0.9
    [Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]

    DNS server: 209.244.0.3 (<name unavailable>)
    1 test failure on this DNS server
    This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.3
    [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    DNS server: 209.244.0.4 (<name unavailable>)
    1 test failure on this DNS server
    This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.4
    [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    Summary of DNS test results:

    Auth Basc Forw Del Dyn RReg Ext
    __________________________________________________ ______________
    Domain: mydomain.com
    bupsrv PASS FAIL FAIL PASS WARN FAIL n/a

    ......................... mydomain.com failed test DNS
    Last edited by dlindie; 4th April 2008, 16:08.

  • #2
    Re: Post NT4 / 2003 Upgrade DNS issue

    Just to confirm
    192.168.0.10 is bupsrv and this machine is your DC and DNS server.

    You have no other DCs so currently you have this servers network card setup with its own IP address (.10) as its DNS IP and no others. (Are there any more NICs and is the windows firewall disabled?)

    Can you make sure of the above and just restart the netlogon service.
    Give it 5 mins and then check DNS locally. Does it have any entries?
    cheers
    Andy

    Please read this before you post:


    Quis custodiet ipsos custodes?

    Comment


    • #3
      Re: Post NT4 / 2003 Upgrade DNS issue

      Can you confirm your Domain name is mydomain.com and not just mydomain?

      This can cause lots of DNS problems

      Best of luck

      W

      Comment

      Working...
      X