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?
Technology Tips and News
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?
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 ?
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