Server 2012 r2 DNS Issues

I currently have 2 sites with 2 Server 2012 R2 domain controllers in each site.

The 2nd site has been just recently added.

Since the addition of the 2nd site I have been slowly moving servers from site A to site B.

Site B (The new site) also has its own independent internet connection.  

I have been experiencing connectivity issues going out to the internet from the new site.  It is intermittent.  Sometimes I can browse the web with no issues and other times I get "Page Cannot be Displayed".  Once this message is received, if I refresh the page it works.

With that being said, I decided to take a packet capture with wireshark and noticed that when the DNS requests are made from a server on the inside of Site B it queries the DNS server at the local site a couple times.... then queries the DNS Server at Site A.

I am assuming I have some DNS issues because it should not be doing that.

I then ran the DNS Betst Practices Analyzer and received the attached output:
I am looking for clarity on the following:

1.  The last Error message states that each Domain Controller should be configured to look at a different DNS server 1st, and have the 2nd DNS entry poit to itself.  Is this correct?  I was always under the assumption that each DC should look to itself 1st, and then another DC 2nd.

2.  Can you please explain the other messages regarding the Root Hint Server and forwarding DNS server?

Please let me know your thoughts....  These issues are not only affecting the outbound internet access, but also affecting inbound connections to my RDS Gateway.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Hypercat (Deb)Commented:
1.  I think you're misinterpreting this error message.  It states that the loopback address should not be first.  However, you're correct that a DNS server should refer to itself first.  So, the first DNS server address should be the local address, but not the loopback address.  EX:  If your DNS server address is, the first DNS server address should be; the SECOND address can be empty, can be the loopback or can be another DNS server.

2.  The other messages indicate that there's some problem reaching the forwarders and some of the root hints. What servers are set as the forwarders? If these are servers at the other site, and you don't want your DNS servers at Site B to query the DNS servers at Site A, then remove them from the list of forwarders.  If these are external servers, then it appears that they're not responding at all or responding very slowly.

     In the case of the root servers, your root list may not be current.  To update the root hints on your DNS server:
BSModlinAuthor Commented:
I am forwarding to External DNS Servers....

The resolution in the BPA staes this:

Configure adapter settings to add the loopback IP address to the list of DNS servers on all active interfaces, but not as the first server in the list.

The loopback address is the same as the IP on the NIC of that server, correct?  If so, why would they want me to have first, and then the loopback?

I am confused.....
Hypercat (Deb)Commented:
The loopback address is not the same as the server's IP; the loopback address for all NIC cards in the world is It literally causes the system to refer any DNS requests back to itself.  I normally don't use it, even though the Technet article says to do so:

"Configure network adapters on this DNS server to use the loopback address (, 0:0:0:0:0:0:0:1, or ::1) as one of the DNS servers, but not as the first DNS server on the list. If the loopback address is configured as the first DNS server, then configure another DNS server first."  

Quoted from

Here's also a post from EE with similar question to yours:

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
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Either configuration is OK, but it is Microsoft's current recommendation to have another DNS listed as the preferred, and itself as the alternate.  This can help with startup delays caused by not being able to reach a DNS server (itself), and DNS islanding.  This is the config I would recommend for all DCs whenever you have more than one at the same site.  When you have a site that has only one DC/DNS, then I would configure it to refer to itself as preferred, and then one at another site as alternate.
David Johnson, CD, MVPOwnerCommented:
uncheck use root hints when forwarders are not available. I've had the same problem with many root hints as well
I'd suggest using dnsbenchmark and use it to guide you in choosing the dns forwarders in your area.. Surprised that Level 3 didn't respond it is one of the fastest here.
BSModlinAuthor Commented:
I found the issue.  It was not the DNS Servers at all.  It was my configuration on a couple of Nexus Switches I have.  Thank you all.
BSModlinAuthor Commented:
I found the issue.  It was not the DNS Servers at all.  It was my configuration on a couple of Nexus Switches I have.  Thank you all.
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
Active Directory

From novice to tech pro — start learning today.