0
I am trying to understand why caching is required on the bind server, when the client receiving the responses would be caching based on TTL values.
So, Is caching required on the server, if the client is not able to cache such responses? Isn't it a overhead on both the client and server systems to cache the same responses at respective ends What are the possible Use cases of caching the responses at the Server? What if there is a dynamic updates of Records on Server and Server still sends the cached Responses?
How did you even arrive at the conclusion that
named
is supposed/required to cache responses? – Daniel B – 2016-08-25T07:57:18.677The TTL timers getting decremented when queried from a client, when the client was not caching responses. Every new query had TTL value lesser than the TTL value of the Zone. This could only mean the server was caching the Responses – Harshith Mulky – 2016-08-26T05:15:33.847