PDC could not be located and DNS errors

I have been running a single Windows 2012 Standard DC for about a year.  It has worked without error and I check the logs frequently and there has never been anything concerning.  Yesterday I installed a new Windows 2012 Standard and promoted it to a domain controller.  First DC=Crete.  Second DC=Corinth.  

I saw logs that SYSVOL successfully replicated and verified by comparing the Netlogon folder.  I checked all the event logs and DNS logs before and after the promotion and all seems well.

Today I moved the PDC and RID to the new server, Corinth.  I ran netdom query fsmo on both DCs and the output reflected current changes.  Again, I checked event logs on both servers and all seems well.

I logged onto a workstation and checked the %logonserver% environment variable and it said the logon server was Crete.  I was expecting it to say Corinth.

I ran dcdiag /c on both DCs and see DNS errors including one that says, "The primary Domain Controller for this domain could not be located.".  I have since moved the PDC and RID back to the first DC and netdom query fsmo is reflecting the change on both DCs.  The PDC not found error seems to have corrected itself because I do not see it in the dcdiag log anymore.

I have attached the dcdiag output from both servers.  I'm concerned that if there are any PDC logon issues that there may be denied logons in my near future.  And I need to correct what ever problems are in my Active Directory so that I can move forward.
crete-dcdiag.log
corinth-dcdiag.log
LVL 4
jekautzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

FOXActive Directory/Exchange EngineerCommented:
Looks like you need a reverse dns entry put in for your new domain controller.  Do that and re run your tests.  Open DNS>reverse lookup and add the entry for the new domain controller.
0
jekautzAuthor Commented:
I see a PTR and NS record for both DCs in the reverse lookup zone.  I ran extensive tests with NSLookup and all seems well.  Could these errors be safe to ignore?  This is an internal domain, why would it or should it try to register with the root hint servers.
0
jekautzAuthor Commented:
The PDC NOT FOUND problem went away last week after I moved it back to the original server, but I still have all of those DNS Root Hint errors and it would seem that they have something to do with IPv6.

I've been researching these errors over the weekend and coming up with different approaches.  One approach caught my attention, but I am unsure if I understand it correctly.  It would seem that a common DNS practice is to use DNS Forwarders and point them at your ISP's DNS servers.  I have no DNS Forwarders.  Is this a good approach to use this instead of Root Servers?  If so, do I delete or disable the Root Servers after setting up Forwarders?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

jekautzAuthor Commented:
Before adding forwarders, I ran dcdiag /test:dns one more time.  Here is that output
Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = CORINTH
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\CORINTH
      Starting test: Connectivity
         ......................... CORINTH passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\CORINTH

      Starting test: DNS

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

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : mydomain

   Running enterprise tests on : mydomain.local
      Starting test: DNS
         Summary of test results for DNS servers used by the above domain
         controllers:

            DNS server: 128.8.10.90 (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 128.8.10.90
            DNS server: 198.32.64.12 (l.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DN
S server 198.32.64.12
            DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:1::803f:235

            DNS server: 2001:500:2::c (c.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:2::c

            DNS server: 2001:500:2d::d (d.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:2d::d

            DNS server: 2001:500:2f::f (f.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:2f::f

            DNS server: 2001:500:3::42 (l.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:3::42

            DNS server: 2001:500:84::b (b.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:500:84::b

            DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:503:ba3e::2:30

            DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:503:c27::2:30

            DNS server: 2001:7fd::1 (k.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:7fd::1

            DNS server: 2001:7fe::53 (i.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:7fe::53

            DNS server: 2001:dc3::35 (m.root-servers.net.)
               1 test failure on this DNS server
               PTR record query for the 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 failed on the DNS server 2001:dc3::35

         ......................... mydomain.local passed test DNS
After adding DNS Forwarders, the same DCDIAG test showed positive results
Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = CORINTH
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\CORINTH
      Starting test: Connectivity
         ......................... CORINTH passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\CORINTH

      Starting test: DNS

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

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : mydomain

   Running enterprise tests on : mydomain.local
      Starting test: DNS
         ......................... mydomain.local passed test DNS
This looks like I achieved positive results, but I'm wondering if I didn't just sweep the IPv6 Root Hint problem under the rug and that maybe I should still resolve it.
0
jekautzAuthor Commented:
The DNS errors disappeared after I added my ISPs DNS servers as DNS forwarders.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jekautzAuthor Commented:
The only comment I received was regarding reverse lookup and that was not the solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.