You're welcome.
--please don't forget to Accept as answer if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is an odd question, kind of a n00b, but does anybody know if there is a way to cache DNS on my windows 2016 server so that it doesn't check for new dns entires for an extended period of time? For example, I want it to keep all records for a minimum of 8 hours. This would be in the event that a major DNS carrier were to go down I would have all the cached for a minimum time.
Thanks
You're welcome.
--please don't forget to Accept as answer if the reply is helpful--
Any DNS being served by my windows server 2016. Obviously for any public DNS it fwd's out, but I was hoping to setup caching that would hold on for a day or so.
So @Anonymous by default, if my windows 2016 server is serving DNS , for any records and the fwder goes down, then it should still be caching those for 1 day, right? One of the major CDN's hosted DNS, but it went down and when it went down we were no longer able to access those records, however, if it was cached for 1 day this should not be the case, correct?
Not on your server. The cache is client side or in other words on the user's desktop pc. You can also manually adjust it via registry hack
Personally I think the better option is to add a more reliable forwarder (8.8.8.8, 8.8.4.4) and add more than one just in case.
Another option is if it was only one or two and fixed name to address you could hard code in the client hosts file.
https://support.microsoft.com/en-us/help/172218/microsoft-tcp-ip-host-name-resolution-order
--please don't forget to Accept as answer if the reply is helpful--
@Anonymous It just occurred to me that if my CDN goes down there is nothing I could do even if caching were set for a month as the provider is down and they're serving the content. Thanks a lot for talking me through this.