Link to home
Start Free TrialLog in
Avatar of EISDC
EISDCFlag for United States of America

asked on

Windows 2010 R2 DNS Server Unable to Qualify FQDN entries from AD Integrated Conditional Forwarders

Servers:
Windows Server 2012 R2
Domain Functional Level:
Windows Server 2012 R2

We are having an issue with two DNS servers, intermittently, and independently not being able to qualify FQDN entries that are queried through conditional forwarders.  Issue seems to occur when a change is performed from on either of the two servers, from within DNS management console.

On the last occurrence of the issue, we only performed a change on a conditional forwarder.  The change was replication "All DNS servers in the forest" to just "All DNS servers in the domain".  After applying the change, we started to experience issues with resolving DNS queries to the domain of the conditional forwarder that was just changed.  Only way correct this issue is to restart the DNS server service on the effected server.

This has happened to 2 different servers both 2012 r2 and to different ad integrated conditional forwarders.  Seems that DNS resolution stops working on 1 server at a time and the fix was always to restart the dns server service.

Has anyone experience this type of behavior with Windows 2010 R2 DNS servers.
ASKER CERTIFIED SOLUTION
Avatar of Mahesh
Mahesh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of EISDC

ASKER

Mahesh,

Thanks for the response to my question.  We are looking closely at memory utilization as being the culprit.  We will be adding additional RAM to the servers

Anthony