Re: Caching DNS
| Newsgroups | gmane.mail.blat |
|---|---|
| Message-ID | <FD09E2A6FC3B4A478E377029AC4C6AB3@stuartnew> |
What we really need at this point is an accurate definition of the problem. DNS servers and clients do not refresh (effectively cache) a fetched DNS record until the TTL (time to live) for the record expires. The TTL is defined by the DNS administrator for the domain in question. If their server cannot handle the load then maybe they need to extend the TTL for their records. I think a "Caching DNS" violates the RFC for Domain Name Servers. Stuart ----- Original Message ----- From: [email protected] [blat] To: [email protected] Sent: Thursday, October 27, 2016 2:20 PM Subject: [blat] Caching DNS My application on an AWS server has been successfully sending emails using BLAT for a long time. Each of my users has a different email server (whatever they use for themselves separately from my application is what they use for my application). Just one of my many users occasionally runs into an error. Their email server's tech support has asked me if I can have my program start using a "caching DNS." Here's where I am naive. I don't know what this means, I don't know if I'm already using a caching DNS, and I don't know how to implement this. Can you advise me? Thank you... Art Lieberman --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus