Lines Matching refs:TTL

77    11.  Resource Record TTL Values and Cache Coherency................23
198    A DNS (or mDNS) packet contains an IP TTL in the IP header, which
200    routing loops. Each Resource Record also contains a TTL, which is
204    types of TTL, the term "IP TTL" is used to refer to the IP header TTL
205    (hop limit), and the term "RR TTL" is used to refer to the Resource
206    Record TTL (cache lifetime).
428    SHOULD be sent with IP TTL set to 255. This is recommended to provide
430    the IP TTL on reception to determine whether the packet originated
620    a TTL value that indicates for how many seconds this answer is valid.
634    an answer is received, then the remaining TTL is reset to the value
642    the record TTL should be added, so that queries are scheduled to be
643    performed at 80-82%, 85-87%, 90-92% and then 95-97% of the TTL.
711    recently (within one quarter of its TTL), then the responder SHOULD
755    with an RR TTL at least half the correct value. If the RR TTL of the
757    RR TTL as known by the Multicast DNS Responder, the responder MUST
761    Because a Multicast DNS Responder will respond if the remaining TTL
762    given in the known answer list is less than half the true TTL, it is
765    records in the known answer list whose remaining TTL is less than
766    half their original TTL. Doing so would simply consume space in the
832    and the TTL in that record is not less than the TTL this host would
986    The resource record TTL given in a legacy unicast response SHOULD NOT
987    be greater than ten seconds, even if the true TTL of the Multicast
1001    of the record's TTL".
1227    Responses for longer than the TTL of the record. The purpose of
1229    peer caches are up to date. After a time interval equal to the TTL of
1252    announcement with TTL zero (see Section 11.2 "Goodbye Packets")
1355 11. Resource Record TTL Values and Cache Coherency
1357    As a general rule, the recommended TTL value for Multicast DNS
1362    The recommended TTL value for other Multicast DNS resource records
1367    of the way to expiry. If the TTL on those records is 75 minutes,
1372    DNS resource records follow the recommendation and have a TTL of 75
1374    a little over an hour. Making the default TTL significantly lower
1405    o If the TTL of B's resource record given in the packet is at least
1406      half the true TTL from A's point of view, then no action is
1409    o If the TTL of B's resource record given in the packet is less than
1410      half the true TTL from A's point of view, then A MUST mark its
1412      from B would use the TTL given by B, and hence may delete the
1414      correcting the TTL, A ensures that the record will be retained for
1428    rrclass and rdata, but an RR TTL of zero. This has the effect of
1429    updating the TTL stored in neighboring hosts' cache entries to zero,
1432    Clients receiving a Multicast DNS Response with a TTL of zero SHOULD
1434    a TTL of 1 and then delete the record one second later. In the case
1581    remaining TTL on all those records to a few seconds so that if the
1616    then, even though its TTL may indicate that it is not yet due to
1655    time, then even though its TTL may indicate that it is not yet due to
1839    transmits two or more gratuitous mDNS announcements setting the TTL
2036    that normal TTL aging is performed on these cached resource records.
2259    * uses DNS TTL 0 to indicate that a record has been deleted