Lines Matching full:record
211 * record's name is to be unique on the network (e.g. SRV records).
225 /* Flag for creating a record for which we will answer remote queries
236 * Currently defined only for DNSServiceReconfirmRecord(), where it forces a record to
238 * concluding that the record is no longer valid and then removing it. This flag should
239 * be used with caution because if a service browsing PTR record is indeed still valid
251 * Similarly, if a query results in a CNAME record, then in addition to following
264 * an associated PTR record.
418 kDNSServiceType_NULL = 10, /* Null resource record. */
445 kDNSServiceType_CERT = 37, /* Certification record */
572 * The full (escaped) DNS name of this service's SRV record would be:
624 * to include P2P. In this case, if a service instance or the record being queried
762 * if the reference was initialized with DNSServiceRegister, and an extra resource record was
987 * create an address record for that host - the application is responsible
988 * for ensuring that the appropriate address record exists, or creating it
998 * txtRecord: The TXT record rdata. A non-NULL txtRecord MUST be a properly formatted DNS
999 * TXT record, i.e. <length byte> <data> <length byte> <data> ...
1001 * i.e. it creates a TXT record of length one containing a single empty string.
1002 * RFC 1035 doesn't allow a TXT record to contain *zero* strings, so a single empty
1003 * string is the smallest legal DNS TXT record.
1043 * Add a record to a registered service. The name of the record will be the same as the
1045 * The record can later be updated or deregistered by passing the RecordRef initialized
1065 * rrtype: The type of the record (e.g. kDNSServiceType_TXT, kDNSServiceType_SRV, etc)
1069 * rdata: The raw rdata to be contained in the added resource record.
1071 * ttl: The time to live of the resource record, in seconds.
1093 * Update a registered resource record. The record must either be:
1094 * - The primary txt record of a service registered via DNSServiceRegister()
1095 * - A record added to a registered service via DNSServiceAddRecord()
1096 * - An individual record registered by DNSServiceRegisterRecord()
1104 * service's primary txt record.
1110 * rdata: The new rdata to be contained in the updated resource record.
1112 * ttl: The time to live of the updated resource record, in seconds.
1133 * Remove a record previously added to a service record set via DNSServiceAddRecord(), or deregister
1134 * an record registered individually via DNSServiceRegisterRecord().
1139 * record being removed was registered via DNSServiceAddRecord()) or by
1140 * DNSServiceCreateConnection() (if the record being removed was registered via
1269 * txt record.
1271 * Note: Applications should NOT use DNSServiceResolve() solely for txt record monitoring - use
1277 * Note: DNSServiceResolve() behaves correctly for typical services that have a single SRV record
1278 * and a single TXT record. To resolve non-standard services with multiple SRV or TXT records,
1304 * txtLen: The length of the txt record, in bytes.
1306 * txtRecord: The service's primary txt record, in standard txt record format.
1403 * Query for an arbitrary DNS record.
1421 * fullname: The resource record's full domain name.
1423 * rrtype: The resource record's type (e.g. kDNSServiceType_PTR, kDNSServiceType_SRV, etc)
1425 * rrclass: The class of the resource record (usually kDNSServiceClass_IN).
1427 * rdlen: The length, in bytes, of the resource record rdata.
1429 * rdata: The raw rdata of the resource record.
1481 * fullname: The full domain name of the resource record to be queried for.
1483 * rrtype: The numerical type of the resource record to be queried for
1486 * rrclass: The class of the resource record (usually kDNSServiceClass_IN).
1649 * Register an individual resource record on a connected DNSServiceRef.
1696 * interfaceIndex: If non-zero, specifies the interface on which to register the record
1698 * family of calls.) Passing 0 causes the record to be registered on all interfaces.
1701 * fullname: The full domain name of the resource record.
1703 * rrtype: The numerical type of the resource record (e.g. kDNSServiceType_PTR, kDNSServiceType_SRV, etc)
1705 * rrclass: The class of the resource record (usually kDNSServiceClass_IN)
1709 * rdata: A pointer to the raw rdata, as it is to appear in the DNS record.
1711 * ttl: The time to live of the resource record, in seconds.
1746 * Instruct the daemon to verify the validity of a resource record that appears
1748 * Causes the record to be flushed from the daemon's cache (as well as all other
1749 * daemons' caches on the network) if the record is determined to be invalid.
1750 * Use this routine conservatively. Reconfirming a record necessarily consumes
1755 * flags: Pass kDNSServiceFlagsForce to force immediate deletion of record,
1758 * interfaceIndex: Specifies the interface of the record in question.
1761 * the caller to be precise about which record should be reconfirmed.
1765 * fullname: The resource record's full domain name.
1767 * rrtype: The resource record's type (e.g. kDNSServiceType_PTR, kDNSServiceType_SRV, etc)
1769 * rrclass: The class of the resource record (usually kDNSServiceClass_IN).
1771 * rdlen: The length, in bytes, of the resource record rdata.
1773 * rdata: The raw rdata of the resource record.
1805 * The client should then record this external IP address and port using whatever
2007 * May be NULL (to construct a PTR record name, e.g.
2031 * TXT Record Construction Functions
2036 * A typical calling sequence for TXT record construction is something like:
2053 * Note: Represents a DNS-SD TXT record.
2073 * the key/value pairs that are to be added to the record.
2086 * Note: When passing parameters to and from these TXT record APIs,
2110 * Releases any resources allocated in the course of preparing a TXT Record
2129 * Keys may exist in four states with respect to a given TXT record:
2132 * - Present with empty value ("key=" appears in TXT record)
2133 * - Present with non-empty value ("key=value" appears in TXT record)
2228 * TXT Record Parsing Functions
2233 * A typical calling sequence for TXT record parsing is something like:
2235 * Receive TXT record data in DNSServiceResolve() callback
2249 * If for some reason you need to parse a TXT record you built yourself
2250 * using the TXT record construction functions above, then you can do
2254 * Most applications only fetch keys they know about from a TXT record and
2262 * Allows you to determine if a given TXT Record contains a specified key.
2264 * txtLen: The size of the received TXT Record.
2266 * txtRecord: Pointer to the received TXT Record bytes.
2270 * return value: Returns 1 if the TXT Record contains the specified key.
2284 * Allows you to retrieve the value for a given key from a TXT Record.
2286 * txtLen: The size of the received TXT Record
2288 * txtRecord: Pointer to the received TXT Record bytes.
2294 * return value: Returns NULL if the key does not exist in this TXT record,
2297 * Returns pointer to location within TXT Record bytes
2314 * Returns the number of keys stored in the TXT Record. The count
2317 * txtLen: The size of the received TXT Record.
2319 * txtRecord: Pointer to the received TXT Record bytes.
2321 * return value: Returns the total number of keys in the TXT Record.
2335 * a TXT Record. Legal index values range from zero to TXTRecordGetCount()-1.
2336 * It's also possible to iterate through keys in a TXT record by simply
2345 * txtLen: The size of the received TXT Record.
2347 * txtRecord: Pointer to the received TXT Record bytes.
2349 * itemIndex: An index into the TXT Record.
2362 * Record bytes that holds the value data.
