Lines Matching full:record
41 the ability to look up DNS resource record data types
76 11. Resource Record TTL Values and Cache Coherency.................28
130 and no new operation codes, response codes, or resource record types.
165 a fully qualified domain name that has an address record. It does
172 routing loops. Each Resource Record also contains a TTL, which is
173 the number of seconds for which the Resource Record may be cached.
185 Record TTL (cache lifetime).
193 resource record sets.
195 A "shared" resource record set is one where several Multicast DNS
199 A "unique" resource record set is one where all the records with
203 rrclass. Before claiming ownership of a unique resource record set,
208 resource record set, but such cooperating responders MUST give
213 record sets, not to individual resource records, but it is sometimes
216 a record that is a member of a "shared" or "unique" resource record
326 names, (i.e. the names of DNS address records), but other DNS record
347 record.
662 the state of that record (e.g. a network browsing window displaying
664 to determine whether the record is still valid.
667 plan to re-query for records after at least 50% of the record
671 The Querier should plan to issue a query at 80% of the record
675 the Multicast DNS Querier has an ongoing interest in the record.
676 If after four queries no answer is received, the record is deleted
679 clients with an active interest. If the expiry of a particular record
683 waste network bandwidth checking whether the record remains valid.
687 the record TTL should be added, so that queries are scheduled to be
763 to the querier. If the responder has not multicast that record
778 multicast announcement of that record is more than a quarter of its
791 records in the local cache, and those record(s) were received with
847 send an answer so as to update the Querier's cache before the record
898 answer record.
933 the network send a response packet containing the same answer record,
934 and the TTL in that record is not less than the TTL this host would
961 answers may be generated because the record answers a question
967 authoritative source for a given record is allowed to issue responses
968 containing that record.
970 The determination of whether a given record answers a given question
971 is done using the standard DNS rules: The record name must match the
972 question name, the record rrtype must match the question qtype
973 (unless the qtype is "ANY"), and the record rrclass must match the
1019 to defend a unique record is a high priority and needs to be done
1022 record in the Authority Section which answers the question in the
1026 the address record for a particular host name, when the host name has
1033 where the answer is a member of a shared resource record set, each
1073 a record on a given interface until at least one second has elapsed
1074 since the last time that record was multicast on that particular
1084 interval of at least 250ms since the last time the record was
1138 The resource record TTL given in a legacy unicast response SHOULD NOT
1140 DNS resource record is higher. This is because Multicast DNS
1142 coherency mechanisms described in Section 11 "Resource Record TTL
1146 mechanisms, could retain stale cached resource record data long after
1150 record in any multicast response recently, it SHOULD schedule the
1151 record to be sent via multicast as well, to facilitate passive
1153 since the record was last sent via multicast is less than one quarter
1154 of the record's TTL".
1169 advertising an HINFO record on each interface as well can be useful
1191 its address record which maps its unique host name to its unique IP
1193 record name and query type T_ANY (255), to elicit answers for all
1198 example, if one host owned the "A" record for "myhost.local.", but
1199 a different host owned the HINFO record for that name.
1205 of its "A" record and all its SRV records [DNS-SD] in the same query
1268 recommended above, any answer containing a record with that name,
1282 its unique resource record set name, rrtype and rrclass cannot
1284 MAY skip the probing step for that resource record set. For example,
1310 populates the Query packets's Authority Section with the record or
1317 name (e.g. the SRV and TXT record describing a DNS-SD service), only
1324 When a host that is probing for a record sees another host issue a
1325 query for the same record, it consults the Authority Section of that
1326 query. If it finds any resource record(s) there which answers the
1327 query, then it compares the data of that (those) resource record(s)
1329 host probing for a single record, receiving a simultaneous probe from
1330 another host also probing for a single record. The two records are
1339 comparing the record class, then the record type, then raw comparison
1341 structure. If the record classes differ, then the numerically greater
1343 record types differ, then the numerically greater type is considered
1350 how and where the record is written into the DNS message; it is not
1351 an intrinsic property of the resource record itself.)
1367 of rdata (in which case the resource record which still has
1383 as value -56, and the wrong address record would be deemed the
1397 described above, that is: if the record classes differ, the record
1399 but the rrtypes differ, the record with the lower rrtype number comes
1402 of advertising DNS-SD services with a TXT record and an SRV record,
1403 the TXT record comes first (the rrtype for TXT is 16) and the SRV
1404 record comes second (the rrtype for SRV is 33).
1437 The most significant bit of the rrclass for a record in the Answer
1486 record, the conflict MUST be resolved as described below in "Conflict
1515 A conflict occurs when a Multicast DNS Responder has a unique record
1517 response packet containing a record with the same name, rrtype and
1525 A common example of a resource record type that is intended to be
1526 unique, not shared between hosts, is the address record that maps a
1528 announce an address record with the same name but a different IP
1530 record is considered to be in conflict.
1541 record in the Answer Section, the Multicast DNS Responder MUST
1542 immediately reset its conflicted unique record to probing state, and
1548 It is very important that any host receiving a resource record that
1560 o Programmatically change the resource record name in an attempt to
1569 o Record this newly chosen name in persistent storage so that the
1612 11. Resource Record TTL Values and Cache Coherency
1615 resource records with a host name as the resource record's name
1616 (e.g. A, AAAA, HINFO, etc.) or contained within the resource record's
1617 rdata (e.g. SRV, reverse mapping PTR record, etc.) is 120 seconds.
1623 when one or more of the resource record(s) in its cache is (are) 80%
1641 resource record with the same name, rrtype and rrclass as one of A's
1644 o If A's resource record is intended to be a shared resource record,
1647 o If A's resource record is intended to be a member of a unique
1648 resource record set owned solely by that responder, then this
1662 resource record with the same name, rrtype and rrclass as one of A's
1665 o If the TTL of B's resource record given in the packet is at least
1669 o If the TTL of B's resource record given in the packet is less than
1671 record to be announced via multicast. Clients receiving the record
1673 record sooner than A expects. By sending its own multicast response
1674 correcting the TTL, A ensures that the record will be retained for
1684 In the case where a host knows that certain resource record data is
1687 response packet, giving the same resource record name, rrtype,
1693 NOT immediately delete the record from the cache, but instead record
1694 a TTL of 1 and then delete the record one second later. In the case
1704 Whenever a host has a resource record with potentially new data (e.g.
1716 these gratuitous announcements, if the record is one that is intended
1718 field of the resource record. This bit, the "cache flush" bit, tells
1719 neighboring hosts that this is not a shared record type. Instead of
1720 merging this new record additively into the cache in addition to any
1727 resource record appears in the Answer Section of the DNS Response, it
1729 resource record appears in the Answer Section of the DNS Response
1757 address record announcement on a wireless interface may be bridged
1787 record. To do so would cause all the other shared versions of this
1788 resource record with different rdata from different Responders to be
1796 Note that the "cache flush" bit is NOT part of the resource record
1798 second 16-bit word of a resource record in the Answer Section of
1800 field), and the actual resource record class is the least-significant
1801 fifteen bits of this field. There is no mDNS resource record class
1802 0x8001. The value 0x8001 in the rrclass field of a resource record in
1803 an mDNS response packet indicates a resource record with class 1,
1804 with the "cache flush" bit set. When receiving a resource record with
1806 off that bit before storing the resource record in memory.
1836 Sometimes a cache record can be determined to be stale when a client
1840 For example, the rdata in an address record can be determined to be
1846 The rdata in an SRV record can be determined to be incorrect if
1850 The rdata in a DNS-SD PTR record can be determined to be incorrect if
1851 attempts to look up the SRV record it references are not successful.
1853 In any such case, the software implementing the mDNS resource record
1858 record, it MUST issue two or more queries for the resource record in
1861 expire, that record SHOULD be promptly flushed from the cache.
1893 If a host sees queries, for which a record in its cache would be
1896 that the record may no longer be valid.
1901 expire, that record MAY be flushed from the cache. The host SHOULD
1902 NOT perform its own queries to re-confirm that the record is truly
1966 particular record type with the name "example.local." does not imply
1968 "child.example.local.", or indeed for other record types with the
1971 Multicast DNS Zones have no SOA record. A conventional DNS zone's
1972 SOA record contains information such as the email address of the zone
2213 device's active records (e.g. a DNS-SD PTR record), it answers on
2333 address record with the name "cheshire.local", then a responder
2334 having an address record with the name "Cheshire.local" should
2342 record for an accented name Y, and a client issues a query for a name
2345 A CNAME record
2347 by the address record for Y.
2379 In the case of a single mDNS Resource Record which is too large to
2381 Responder SHOULD send the Resource Record alone, in a single IP
2391 using fragments, MUST NOT contain more than one Resource Record.
2498 to record this fact, and wait for those additional Known Answer
2579 rrclass field is used to indicate that the record is a member of a
2663 the familiar APIs, naming syntax, resource record types, etc., of
2674 * uses UTF-8, and only UTF-8, to encode resource record names
2686 * uses DNS TTL 0 to indicate that a record has been deleted
2842 set of host names and other DNS resource record names, in the absence
