Windows 10: Is it possible to audit a DC or DNS server for DNS lookups from clients?

Hi folks,I'm looking to reduce our overall domain controller footprint and the first consideration is DNS lookups from the clients against their local domain controllers.Is there a way to audit the DC itself for who's doing lookups against it?

:)

 

dns client resolvers not looking for 2nd DNS server when primary DNS server is off line

hi

i have a situation on a couple of domain networks where the client computers lose internet browsing (dns resolution) when the primary listed dns server goes off line.

i made the assumption that the client pc would imediately look to the secondary named dns server listed on its NIC ipv4 settings.

i have read a few articles from over 10 years ago that explains that it is the protocol that all vendors have to follow that causes this problem and that an ipconfig /flushdns will resolve the problem and the client will then find the secondary dns server.

can you tell me if there is a better solution or configuration that will remove the need for the end user to have to call tech support to fix their problem of not being able to web browse?

can DNS servers be clustered to prevent single point of contact failure? if so is it simple to configure?

if i point my primary dns to the firewall instead of the DC(DNS server) will this still allow for a speedy domain authentication?

are there any other solutions that you know of?

many thanks

 

DNS Servers

So far, it seems like I got it fixed. I disabled Advanced DNS Service and DNS Relay. I put in the two DNS server IPs I listed above into the internet configuration and rebooted it.

 

DNS SERVER NOT RESONDING

Hi Rita French,

This issue often occurs when the DNS settings are incorrect. I suggest you to perform the following methods to troubleshoot the issue.

Method 1:

I would recommend you to change the Preferred DNS server and check if it helps.

• Press Windows + R keys to open Run window, type
  ncpa.cpl and press Enter.
• Right-click on the connection that you use for the local connection, and then click
  Properties.
• Click to select Internet Protocol Version 4 (TCP/IPv4), and then click
  Properties.
• In the Internet Protocol window, let's change the Preferred DNS server to
  208.67.222.222
• Click OK twice to complete the modification.

Note: If the issue persists, please repeat the steps and change the "Preferred DNS server" to 208.67.220.220.

Method 2:

If that does not help, try to flush the DNS. Follow these steps below.

• From Start screen, type Command Prompt.
• Right-click on Command Prompt and choose Run as Administrator.
• Type: ipconfig /flushdns and press Enter.

Note: The ipconfig /flushdns command provides you with a means to flush and reset the contents of the DNS client resolver cache. During DNS troubleshooting, if necessary, you can use this procedure to discard negative cache entries from the cache, as well
as, any other dynamically added entries.

Hope any of these methods help!

Kind regards,

Leon