Announcement

Collapse
No announcement yet.

DNS Error After the Upgrade

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

  • DNS Error After the Upgrade

    Hi,

    Can anyone help me, for the problem what i am facing in my organization?

    I am having a windows server 2003 SP2 Domain with about 250 Odd cilents. And yesterday I had upgraded one of my server 2008R2 as an additional domain controller, which was a member server.
    I followed all the steps properly and while upgrading the server to ADC I have not received any error message. Now my problem is whenever I tried to open the DNS console of the new ADC it is coming with a message saying that the xxserver is not available do you want to connect it anyway? Evern if I click on Yes and restart the ADC the same message appears. But after clicking yes it is showing up all the DNS entries.
    I checked the services, and Event Viewer. The DNS services are running fine, but I am getting an error message:
    The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "000021A2: SvcErr: DSID-030A0AE6, problem 5012 (DIR_ERROR), data 8610". The event data contains the error.

    Can anyone help me on this? When ever I run the NSLOOKUP I am not able to see the DC and ADC resolved, but it works perfectly on my DC.

    I hope my question is clear; please someone can help me on this?

    I followed the below steps while adding the server 2008r2 as the ADC
    1. Raise Domain Functional Level
    2. Prepare current Windows 2003 Active Directory for Windows Server 2008 domain controllers.
    3. Then made the server 2008R2 client as the ADC.
    4. Transfer FSMO roles to the Windows Server 2008 Domain Controller

  • #2
    Re: DNS Error After the Upgrade

    So is AD functioning OK and DNS not, or are both not working?

    IMHO start by uninstalling the DNS role (from what you say, you have other DNS servers) and reinstalling it
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: DNS Error After the Upgrade

      Hi,

      Can you provide DC diag and Netdiag report? It will do standard test for AD DNS functionality and report failure if found.
      Thanks & Regards
      v-2nas

      MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
      Sr. Wintel Eng. (Investment Bank)
      Independent IT Consultant and Architect
      Blog: http://www.exchadtech.blogspot.com

      Show your appreciation for my help by giving reputation points

      Comment


      • #4
        Re: DNS Error After the Upgrade

        Originally posted by Ossian View Post
        So is AD functioning OK and DNS not, or are both not working?

        IMHO start by uninstalling the DNS role (from what you say, you have other DNS servers) and reinstalling it
        Sorry u mean to uninstall the DNS from the DC? or from this ADC?

        Comment


        • #5
          Re: DNS Error After the Upgrade

          Hi below is the DC diag result:

          Doing primary tests

          Testing server: Default-First-Site-Name\GWPSVIRTUAL
          Starting test: Advertising
          ......................... GWPSVIRTUAL passed test Advertising
          Starting test: FrsEvent
          There are warning or error events within the last 24 hours after the
          SYSVOL has been shared. Failing SYSVOL replication problems may cause
          Group Policy problems.
          ......................... GWPSVIRTUAL passed test FrsEvent
          Starting test: DFSREvent
          ......................... GWPSVIRTUAL passed test DFSREvent
          Starting test: SysVolCheck
          ......................... GWPSVIRTUAL passed test SysVolCheck
          Starting test: KccEvent
          ......................... GWPSVIRTUAL passed test KccEvent
          Starting test: KnowsOfRoleHolders
          ......................... GWPSVIRTUAL passed test KnowsOfRoleHolders
          Starting test: MachineAccount
          ......................... GWPSVIRTUAL passed test MachineAccount
          Starting test: NCSecDesc
          Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
          Replicating Directory Changes In Filtered Set
          access rights for the naming context:
          DC=ForestDnsZones,DC=domainname,DC=ae
          Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
          Replicating Directory Changes In Filtered Set
          access rights for the naming context:
          DC=DomainDnsZones,DC=domainname,DC=ae
          ......................... GWPSVIRTUAL failed test NCSecDesc
          Starting test: NetLogons
          ......................... GWPSVIRTUAL passed test NetLogons
          Starting test: ObjectsReplicated
          ......................... GWPSVIRTUAL passed test ObjectsReplicated
          Starting test: Replications
          ......................... GWPSVIRTUAL passed test Replications
          Starting test: RidManager
          ......................... GWPSVIRTUAL passed test RidManager
          Starting test: Services
          IsmServ Service is stopped on [GWPSVIRTUAL]
          ......................... GWPSVIRTUAL failed test Services
          Starting test: SystemLog
          An error event occurred. EventID: 0x00000457
          Time Generated: 12/08/2010 10:44:33
          Event String:
          all the driver before you log in again.
          An error event occurred. EventID: 0x00000457
          Time Generated: 12/08/2010 10:44:34
          A warning event occurred. EventID: 0x000003F6
          Time Generated: 12/08/2010 10:54:13
          Event String:
          Name resolution for the name 1.0.0.127.in-addr.arpa timed out after
          none of the configured DNS servers responded.
          A warning event occurred. EventID: 0x00001695
          Time Generated: 12/08/2010 10:54:21
          Event String:
          Dynamic registration or deletion of one or more DNS records associat
          ed with DNS domain 'domainname.' failed. These records are used by other comput
          ers to locate this server as a domain controller (if the specified domain is an
          Active Directory domain) or as an LDAP server (if the specified domain is an app
          lication partition).
          A warning event occurred. EventID: 0x00001695
          Time Generated: 12/08/2010 10:54:21
          Event String:
          Dynamic registration or deletion of one or more DNS records associat
          ed with DNS domain 'DomainDnsZones.domainname.' failed. These records are used
          by other computers to locate this server as a domain controller (if the specifie
          d domain is an Active Directory domain) or as an LDAP server (if the specified d
          omain is an application partition).
          A warning event occurred. EventID: 0x00001695
          Time Generated: 12/08/2010 10:54:21
          Event String:
          Dynamic registration or deletion of one or more DNS records associat
          ed with DNS domain 'ForestDnsZones.domainname.' failed. These records are used
          by other computers to locate this server as a domain controller (if the specifie
          d domain is an Active Directory domain) or as an LDAP server (if the specified d
          omain is an application partition).
          ......................... GWPSVIRTUAL failed test SystemLog
          Starting test: VerifyReferences
          ......................... GWPSVIRTUAL passed test VerifyReferences


          Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
          ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
          ......................... ForestDnsZones passed test
          CrossRefValidation

          Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
          ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
          ......................... DomainDnsZones passed test
          CrossRefValidation

          Running partition tests on : Schema
          Starting test: CheckSDRefDom
          ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
          ......................... Schema passed test CrossRefValidation

          Running partition tests on : Configuration
          Starting test: CheckSDRefDom
          ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
          ......................... Configuration passed test CrossRefValidation

          Running partition tests on : domainname
          Starting test: CheckSDRefDom
          ......................... domainname passed test CheckSDRefDom
          Starting test: CrossRefValidation
          ......................... domainname passed test CrossRefValidation

          Running enterprise tests on : domainname
          Starting test: LocatorCheck
          ......................... domainname passed test LocatorCheck
          Starting test: Intersite
          ......................... domainname passed test Intersite

          C:\Users\Administrator.domainname>

          My DC is a DNS server, But before downgrading the DC i want to confirm that the ADC is working properly

          Comment


          • #6
            Re: DNS Error After the Upgrade

            Possible causes of failure include:
            - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers
            - Specified preferred and alternate DNS servers are not running
            - DNS server(s) primary for the records to be registered is not running
            - Preferred or alternate DNS servers are configured with wrong root hints
            - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration

            USER ACTION
            Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt or by restarting Net Logon service. Nltest.exe is available in the Microsoft Windows Server Resource Kit CD.

            Comment


            • #7
              Re: DNS Error After the Upgrade

              Hi,
              Thanks for the reply.

              I had checked the IP address configuration, and the DNS server is mentioned properly , i am able to ping with the AD ( dns server)
              The DNS server also i checked, it is resolving the name with NSLOOKUP : resolving the new ADC and also any of the PC in my domain.
              Will it be alright if i uninstall the DNS service from the ADC? Should i be making any changes in the DNS in the AD? Which is the root DNS server?

              Comment


              • #8
                Re: DNS Error After the Upgrade

                Hi,

                Don't uninstall DNS from ADC right now. Please specifiy what is the operational difficulty that you have ended up due to the error.

                What are you trying to achive?
                Thanks & Regards
                v-2nas

                MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
                Sr. Wintel Eng. (Investment Bank)
                Independent IT Consultant and Architect
                Blog: http://www.exchadtech.blogspot.com

                Show your appreciation for my help by giving reputation points

                Comment


                • #9
                  Re: DNS Error After the Upgrade

                  Thanks for the reply,
                  Basically i want to upgrade my domain to server 2008R2 . so that i can start using the new features that come aong with the 2008R2 server. For this same purpose only i upgraded one of my member server into ADC. So before demoting my DC i want to confirm that everything is working fine, so that i can demote the DC.
                  This is my intention to achieve, But DNS is not working with my new ADC. when i try nslookup in new ADC it is giving me some strange numbers. I hope you can help me on this
                  C:\Users\Administrator.domainname>nslookup
                  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
                  primary name server = 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
                  responsible mail addr = (root)
                  serial = 0
                  refresh = 28800 (8 hours)
                  retry = 7200 (2 hours)
                  expire = 604800 (7 days)
                  default TTL = 86400 (1 day)
                  Default Server: UnKnown
                  Address: ::1

                  Comment


                  • #10
                    Re: DNS Error After the Upgrade

                    Hi,

                    are you using IP v6. If not then disable it from network connections property.
                    Then try nslookup again.

                    Verify the DNS enteries. and is your ADC setup as DNS server.

                    you can use
                    nslookup> server IP_Address_ADC
                    This will force nslookup to use ADC as dns server.

                    then try to resolve names.
                    Last edited by v-2nas; 9th December 2010, 18:52. Reason: more info
                    Thanks & Regards
                    v-2nas

                    MCTS 2008, MCTIP, MCSE 2003, MCSA+Messaging E2K3, MCP, E2K7
                    Sr. Wintel Eng. (Investment Bank)
                    Independent IT Consultant and Architect
                    Blog: http://www.exchadtech.blogspot.com

                    Show your appreciation for my help by giving reputation points

                    Comment


                    • #11
                      Re: DNS Error After the Upgrade

                      Hi,

                      I am not using IPV6 i will try to disable and see....... before making the ADC as DNS server.. can i please ask if i can revert back to the DC if the ADC DNS Service is not running?? Otherwise i am not going to try for it coz this is my live environment...

                      Comment


                      • #12
                        Re: DNS Error After the Upgrade

                        Now i disabled the IPV6 and now the nslookup is working, but i am getting the same error
                        :The server "servername" could not be contacted, The error was "the service is unavailable" . Would you like to connect it anyway?

                        Is there anyway that DNS can be start it self, if i click yes for this and If i start the DNS service then the DNS shows all the entries......

                        Help please

                        Originally posted by v-2nas View Post
                        Hi,

                        are you using IP v6. If not then disable it from network connections property.
                        Then try nslookup again.

                        Verify the DNS enteries. and is your ADC setup as DNS server.

                        you can use
                        nslookup> server IP_Address_ADC
                        This will force nslookup to use ADC as dns server.

                        then try to resolve names.

                        Comment


                        • #13
                          Re: DNS Error After the Upgrade

                          What are your ipconfig /all details from the server???

                          Is your reverse lookup zone 127.0.0.x???

                          Are you using 127.0.0.x for your DNS server??? If you are please chang this to the actual IP address of the server.

                          Comment


                          • #14
                            Re: DNS Error After the Upgrade

                            Originally posted by wullieb1 View Post
                            What are your ipconfig /all details from the server???

                            This shows my IPV6 address with some strange number also... copied below:

                            Link-local IPv6 Address . . . . . : fe80::80a7:93c9:e128:2fdf%1
                            IPv4 Address. . . . . . . . . . . : 10.20.0.11
                            Subnet Mask . . . . . . . . . . . : 255.255.0.0
                            Default Gateway . . . . . . . . . : 10.20.0.7


                            Is your reverse lookup zone 127.0.0.x???

                            No, my DNS entries showing in this ADC is excactly the same as the DC no 127.0.0.X zone......

                            Are you using 127.0.0.x for your DNS server??? If you are please chang this to the actual IP address of the server.
                            I am not using the 127 Zone in DNS server ( DC). My DNS server (DC) is working perfectly fine, and the Entries in the ADC is also showing up everything what is there in DC, but i am getting an error message whenever i restart the ADC and try to open the DNS console....
                            Would like to get a solution out of this, so that i can demote the DC ( server 2003) and make my ADC as the PDC

                            Comment


                            • #15
                              Re: DNS Error After the Upgrade

                              Your reverse lookup zones are configured with 127.0.0.x

                              A warning event occurred. EventID: 0x000003F6
                              Time Generated: 12/08/2010 10:54:13
                              Event String:
                              Name resolution for the name 1.0.0.127.in-addr.arpa timed out after
                              none of the configured DNS servers responded.
                              Delete that zone and use the range you are on.

                              Also have you disabled IPv6 on the network card properties???
                              Last edited by wullieb1; 13th December 2010, 10:12.

                              Comment

                              Working...
                              X