DNS dynamic update for client
bencmcb
Users Awaiting Email Confirmation Posts: 43 ■■□□□□□□□□
I double click the A Resource Record for computer2 on the dns console installed on computer1, i see that the TTL value is 20 minutes. Does this mean that the Resource Record for computer2 will only stay for 20 minutes on the cache of the client that had queried for computer2?
That confuses me because the "minimum (default) TTL" and "TTL for this record" settings under the SOA tab are all set to 1 hour. I thought that would determine how long the Resource Record would stay in the cache.
That confuses me because the "minimum (default) TTL" and "TTL for this record" settings under the SOA tab are all set to 1 hour. I thought that would determine how long the Resource Record would stay in the cache.
Comments
-
thatguy85
Member Posts: 41 ■■□□□□□□□□
Basically, it works like this:
Minimum (Default) TTL: You specify this in the SOA tab of the zone. It determines the default TTL that is applied to all resource records in the zone. TTL values aren't relevant for resource records within their authoritative zones though, only when the record is in a non-authoritative space.
TTL For This Record: The value you configure here determines the TTL of the present SOA resource record. It overrides the default value setting in the previous field. -
bencmcb
Users Awaiting Email Confirmation Posts: 43 ■■□□□□□□□□
computer2 resource record was in an authoritative space, why did that only have 20 mins for TTL when I double clicked on it?
-
thatguy85
Member Posts: 41 ■■□□□□□□□□
No idea.
Google searching didn't come up with much that was useful.