Lines Matching refs:TTL
68 4. IP TTL Checks..................................................8
77 13. Resource Record TTL Values and Cache Coherency................25
192 A DNS (or mDNS) packet contains an IP TTL in the IP header, which
194 routing loops. Each Resource Record also contains a TTL, which is
198 types of TTL, the term "IP TTL" is used to refer to the IP header TTL
199 (hop limit), and the term "RR TTL" is used to refer to the Resource
200 Record TTL (cache lifetime).
411 4. IP TTL Checks
414 MUST be sent with IP TTL set to 255.
418 verify that the IP TTL in response packets is 255, and silently
419 discard any response packets where the IP TTL is not 255. Without
427 (or equivalent API) for obtaining the IP TTL of received packets.
436 were to discard queries where the TTL is not 255, they would not
569 a TTL value that indicates for how many seconds this answer is valid.
588 then the remaining TTL is reset to the value given in the answer, and
595 the record TTL should be added, so that queries are scheduled to be
596 performed at 80-82%, 85-87%, 90-92% and then 95-97% of the TTL.
664 recently (within one quarter of its TTL), then the responder SHOULD
715 with an RR TTL at least half the correct value. If the RR TTL of the
717 RR TTL as known by the Multicast DNS Responder, the responder MUST
721 Because a Multicast DNS Responder will respond if the remaining TTL
722 given in the known answer list is less than half the true TTL, it is
725 records in the known answer list whose remaining TTL is less than
726 half their original TTL. Doing so would simply consume space in the
789 and the TTL in that record is not less than the TTL this host would
902 The resource record TTL given in a unicast response SHOULD NOT be
903 greater than ten seconds, even if the true TTL of the Multicast DNS
917 of the record's TTL".
1124 Responses for longer than the TTL of the record. The purpose of
1126 peer caches are up to date. After a time interval equal to the TTL of
1375 13. Resource Record TTL Values and Cache Coherency
1377 The recommended TTL value for Multicast DNS resource records is
1382 of the way to expiry. If the TTL on those records is 120 minutes,
1387 DNS resource records follow the recommendation and have a TTL of 120
1389 up to two hours. Making the default TTL significantly lower would
1421 o If the TTL of B's resource record given in the packet is at least
1422 half the true TTL from A's point of view, then no action is
1425 o If the TTL of B's resource record given in the packet is less than
1426 half the true TTL from A's point of view, then A MUST mark its
1428 from B would use the TTL given by B, and hence may delete the
1430 correcting the TTL, A ensures that the record will be retained for
1444 and rdata, but an RR TTL of zero. This has the effect of updating the
1445 TTL stored in neighbouring hosts' cache entries to zero, causing that
1455 Clients receiving a Multicast DNS Response with a TTL of zero SHOULD
1457 a TTL of 1 and then delete the record one second later. In the case
1592 remaining TTL on all those records to a few seconds so that if the
1632 then, even though its TTL may indicate that it is not yet due to
1665 time, then even though its TTL may indicate that it is not yet due to
1767 transmits two or more gratuitous mDNS announcements setting the TTL
1912 that normal TTL aging is performed on these cashed resource records.
2119 * uses DNS TTL 0 to indicate that a record has been deleted
2120 * uses IP TTL 255 to verify that answers originated on the local link