Lines Matching full:record
78 6.2 DNS TXT Record Format Rules for use in DNS-SD..................12
79 6.3 DNS-SD TXT Record Size.........................................14
82 6.6 Example TXT Record.............................................16
91 14. DNS Additional Record Generation...............................24
133 and no new operation codes, response codes, resource record types,
135 a convention for how existing resource record types can be named and
258 SRV record "_ipp._tcp.example.com." to find the list of IPP printers
598 contact that service, it sends a DNS query for the SRV record of
601 The result of the DNS query is a SRV record giving the port number
625 However, the DNS packet format and record format still require a host
626 name to link the target host referenced in the SRV record to the
629 SRV record may give its own name as the name of the target host, and
633 restriction being that a given name may not have both a CNAME record
667 record with the same name as the SRV record. The specific nature of
669 but the overall syntax of the data in the TXT record is standardized,
675 A DNS TXT record can be up to 65535 (0xFFFF) bytes long. The total
676 length is indicated by the length given in the resource record header
683 The format of the data within a DNS TXT record is zero or more
687 The format of each constituent string within the DNS TXT record is a
695 6.2 DNS TXT Record Format Rules for use in DNS-SD
700 DNS TXT record, in the form "name=value". Everything up to the first
716 Using this standardized name/value syntax within the TXT record makes
719 attribute names in a service TXT record, it MUST silently ignore them.
722 are given in the SRV record. This information -- target host name and
724 the TXT record.
740 record. In this case, the information in the TXT record should be
742 instances of a service, the TXT record allows the client to know some
746 that the information in the TXT record is in agreement with the
751 information in the TXT record. For example, when printing using the
755 appropriate to embed this information in the TXT record, because the
772 6.3 DNS-SD TXT Record Size
774 The total size of a typical DNS-SD TXT record is intended to be small
783 the TXT record under 1300 bytes should allow it to fit in a single
809 attribute name may appear at most once in a TXT record. If a client
810 receives a TXT record containing the same attribute name more than
813 a DNS-SD TXT record from start to end, placing name/value pairs into
819 the TXT record for the requested name, they should search the TXT
820 record from the start, and simply return the first matching name they
831 When examining a TXT record for a given named attribute, there are
916 size of the TXT record, without atually making the data any more
920 6.6 Example TXT Record
922 The TXT record below contains three syntactically valid name/value
953 it to be the first name/value pair in the TXT record. This
954 information in the TXT record can be useful to help clients maintain
964 of the TXT record specification being used to create this TXT record,
967 DNS-SD TXT record specification starts at txtvers=1 and stays that
974 record.
1102 As with the TXT record name/value pairs, the list of possible
1176 creates a placeholder SRV record (priority=0, weight=0, port=0,
1186 attempts to create this SRV record, it finds that a record with the
1189 the class, and it must choose another. If no SRV record already
1192 they try to use it. The SRV record needs to contain the target host
1203 No PTR record is created advertising the presence of empty flagship
1222 a list of PTR records, where the rdata of each PTR record is the
1362 14. DNS Additional Record Generation
1377 When including a PTR record in a response packet, the
1380 o The SRV record(s) named in the PTR rdata.
1381 o The TXT record(s) named in the PTR rdata.
1387 When including an SVR record in a response packet, the
1395 When including a TXT record in a response packet, no additional
1399 14.4 Other Record Types
1401 In response to address queries, or other record types, no additional
1601 SRV record's target host is given by the appropriate IPv6 address
1602 records instead of the IPv4 "A" record.
