Announcement

Collapse
No announcement yet.

DNS error on server 2003

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

  • DNS error on server 2003

    Hi,

    I've run netdiag and I keep getting this and I'm not sure why.

    I can resolve the dns name in forward and backwards.

    I see entries for that server in the DNS console.

    running netdiag /fix didn't do anything. What is it complaining about?


    DNS test . . . . . . . . . . . . . : Passed
    [WARNING] Cannot find a primary authoritative DNS server for the name
    'dc1.eng.ad.btu.com.'. [ERROR_TIMEOUT]
    The name 'dc1.eng.ad.btu.com.' may not be registered in DNS.
    PASS - All the DNS entries for DC are registered on DNS server '127.123.16.4
    1' and other DCs also have some of the names registered.


    The server is running as Windows server 2003 in windows 2003 domain mode.

    it is a child to a windows 2000 forest in windows 2000 mixed mode.

    the forest root domain is: ad.btu.com

    tne domain that dc1 is hosting is "eng"

  • #2
    Re: DNS error on server 2003

    Is 'dc1.eng.ad.btu.com register in the correct DNS server with all its resource (SRV, A etc.)?
    Is there PTR record for this server? If no, this a good time to add PTR record to the server....
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: DNS error on server 2003

      yes there is a ptr record.


      under the foward lookup,

      there is:

      _msdcs \ dc \ sites \ ad \ _tcp and 2 SRV records: _kerberos and _ldap both of which refer to dc1.eng.ad.btu.com

      _msdcs \ dc \ _tcp and 2 SRV records: _kerberos and _ldap both of which refer to dc1.eng.ad.btu.com

      _msdcs \ PDC \ _tcp is an _ldap record


      _sites \ ad \ _tcp are 2 SRV records: _kerberos and _ldap

      _tcp there are 3 SRV records: _kerberos, _kpasswd, _ldap

      _udp there are 2 SRV records: _kerberos, _kpasswd


      in the root of the fwd lookup zone there are:

      1 SOA record for dc1.eng.ad.btu.com
      1 NS record for dc1.eng.ad.btu.com
      1 host (a) for (same as parent folder) to the ip address associated with dc1.eng.ad.btu.com
      1 host (a) for (same as parent folder) to 169.254.200.52 (same server, just it has 2 nic cards)
      1 host(a) for the server name


      I ran a dcdiag /test:dns and the output below:

      Domain Controller Diagnosis

      Performing initial setup:
      Done gathering initial info.

      Doing initial required tests

      Testing server: AD\DC1
      Starting test: Connectivity
      The host 1e1623d4-0fe3-4eaf-8a12-e2a63e47ac86._msdcs.ad.btu.com could n
      ot be resolved to an
      IP address. Check the DNS server, DHCP, server name, etc
      Although the Guid DNS name
      (1e1623d4-0fe3-4eaf-8a12-e2a63e47ac86._msdcs.ad.btu.com) couldn't be
      resolved, the server name (rohan.dceng.ad.scu.edu) resolved to the IP
      address ('127.123.16.4) and was pingable. Check that the IP address
      is registered correctly with the DNS server.
      ......................... DC1 failed test Connectivity

      Doing primary tests

      Testing server: AD\dc1

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

      Running partition tests on : eng

      Running partition tests on : Schema

      Running partition tests on : Configuration

      Running enterprise tests on : ad.btu.com
      Starting test: DNS
      Test results for domain controllers:

      DC: dc1.eng.ad.btu.com
      Domain: eng.ad.btu.com


      TEST: Basic (Basc)
      Error: No LDAP connectivity

      Summary of DNS test results:

      Auth Basc Forw Del Dyn RReg Ext
      __________________________________________________ ______________
      Domain: eng.ad.btu.com
      dc1 PASS FAIL PASS PASS PASS PASS n/a

      ......................... ad.btu.com failed test DNS



      ---------------------------------------------


      I'm not sure where the problem lies. Is it the server itself cannot resolve its name, or other dns servers in the same forest doesn't have its record. The basic test failed on ldap connectivity, but is that internal to the domain or going out communicating with the ad.btu.com forest?
      Last edited by roguecoolman; 7th November 2005, 18:44.

      Comment


      • #4
        Re: DNS error on server 2003

        > 169.254.200.52

        Bad. That may be the cause of the LDAP error. Never have unreachable IP's in your DNS.

        > Cannot find a primary authoritative DNS server for the name

        So... where do you host the zone for eng.ad.btu.com? do you have proper forwarders and delegations?

        Comment


        • #5
          Re: DNS error on server 2003

          i host eng.ad.btu.com on dc1 as an ad-integrated zone.
          I've forwarded to our unix dns servers.
          The server is confgured in its tcp/ip settings to only use itself as a dns server.

          Delegations? as in which servers can zone transfer with the dns server?


          I've also deleted the unreachable ip address.

          Comment


          • #6
            Re: DNS error on server 2003

            Originally posted by roguecoolman
            I've also deleted the unreachable ip address.
            169.254.200.52 is an APIPA address and should not be configured in DNS.
            Just disable the unused NIC on the DC and delete all the references to this address in the DNS
            Guy Teverovsky
            "Smith & Wesson - the original point and click interface"

            Comment


            • #7
              Re: DNS error on server 2003

              looks like that was the culprit.

              the bad apipa entry. I wish the dns test output was more specific on that..


              but looks good now. I have no errors.

              I should put you guys on the pay roll!

              Comment

              Working...
              X