DiscussWorldIssues - Socio-Economic Religion and Political Uncensored Debate - View Single Post - Active Directory - Wish to learn and find out whats going on

**Psymoussy** · 03-11-2011, 10:41 PM

True, but most were out of my hands I think as many were that it could not find someinternetserver.com.

Anyway, it was a .local domain and I wasn't forwarding traffic through the AD server - I configured all the NICs to use our ISP's DNS in primary and our local DNS server as the secondary and the server was set to forward requests, again, to the ISP's DNS. Gateway was set to the router.

I'd be inclined that sites that could not be resolved by the primary were attempted to be requested by our DNS server, not resolved due to site not existing any more, then thrown up as an error in the event log.

Your PC's should only be using the local DNS (AD server). Your DNS server should be set to forward requests it can't answer to your ISP. I use opendns myself. If you don't do it this way, you are just asking for trouble in an AD environment.

03-11-2011, 10:41 PM	#9
Psymoussy Join Date Oct 2005 Posts 458 Senior Member	True, but most were out of my hands I think as many were that it could not find someinternetserver.com. Anyway, it was a .local domain and I wasn't forwarding traffic through the AD server - I configured all the NICs to use our ISP's DNS in primary and our local DNS server as the secondary and the server was set to forward requests, again, to the ISP's DNS. Gateway was set to the router. I'd be inclined that sites that could not be resolved by the primary were attempted to be requested by our DNS server, not resolved due to site not existing any more, then thrown up as an error in the event log. Your PC's should only be using the local DNS (AD server). Your DNS server should be set to forward requests it can't answer to your ISP. I use opendns myself. If you don't do it this way, you are just asking for trouble in an AD environment.
	Quote