Active Directory with two DNS servers(Primary and Secondary) . Client using primary with a public DNS as secondary

I understand Active Directory uses DNS to support the structure of AD Roles and if I'm not mistaken authentication also. 

What are the specific issues with using a public DNS ip as a secondary DNS address?

September 2nd, 2015 11:55am

It would make more sense to add public as tertiary (3rd in line of DNS servers) so that primary and secondary could use internal AD servers.  I would always ensure AD connectivity first over anything else..
Free Windows Admin Tool Kit Click here and download it now
September 2nd, 2015 1:17pm

Ok, but what specific issues would arise using public ip as the secondary.

I understand if the client can't get a response from the primary dns it goes to the secondary, how long does that take and once its using the secondary, how often does it query the primary for availability ? 


September 2nd, 2015 1:34pm

Hi Sysnettech,

When querying, a client would send query to primary DNS server first. And wait 1 second for a response. If it doesn't get a response, it would send query to secondary DNS server.

If it sends another query, it would still follow the same process.

Here is the reference:
DNS Clients:
https://technet.microsoft.com/en-us/library/dn593685.aspx

Best Regards,

Leo

Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2015 1:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics