Windows 10: mixing external and internal DNS servers for ad joined machines

Hi


I have a question. Many of our clients have only one DC. Is it better to use external DNS ISP,or google as the secondary DNS server for AD-joined machines or set up a conditional forwarder in the firewall and set the DNS server as the firewall's IP. In the later scenario, if the DC goes down, they can still access the internet.

:)

 

Non-AD Integrated DNS Servers

Non-AD Integrated DNS Servers





Hi everyone



We’re in a situation that demands for deploying non-AD integrated DNS (I’m refraining myself explaining why to keep the focus to the actual question). It is going to be a member Windows DNS server joined to the AD domain (say abc.com), but would be hosting
disjoint DNS Zones (say xyz.com).



I’m evaluating the downside of doing it when compared to using AD-integrated DNS and identified couple of them as below – would appreciate inputs from the community if there’s anything else that I’m missing out OR correct me if at all the below concerns
are invalid:



Downsides of Deploying non-AD integrated DNS:



1. We compromise on the out-of-the-box AD-integrated replication of DNS and have to build this manually to make the DNS service highly-available.



2. Will the domain (abc.com) joined machines be able to dynamically register ‘A’ records in this DNS server?



I know when the DNS is AD-integrated, the domain joined systems are authenticated and can dynamically register ‘A’ (and other records) in the DNS. However, in this case the DNS server (although the member of the same domain), is hosting
non-AD integrated DNS zones. Will the machines be able to register to DNS zone by default, or some configuration would be needed to all the machines?





Thanks

 

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

 

DNS Servers

I run a DNS server locally, so when a domain is already cached, I get it back almost instantly, otherwise it responds as fast as the first server in my list (75.75.75.75 in my case.)