Searched refs:DNS (Results 1 - 7 of 7) sorted by relevance

/seL4-camkes-master/projects/picotcp/docs/user_manual/
H A Dchap_api_dns_sd.tex1 \section{DNS SD client}
4 With this module DNS-SD services can be registered on the network to allow Zero Configuration Networking on the device. This is merely a small layer on top of Multicast DNS.
15 Registers the service with a certain name and type on the network via Multicast DNS.
32 \item \texttt{txt$\_$data} - Pointer to vector with key-value pairs to insert into the TXT record to give additional information about the service. Use the 'PICO$\_$DNS$\_$SD$\_$KV$\_$VECTOR$\_$DECLARE'-macro to declare a vector for key-value-pairs. This vector will be destroyed when the function returns since there's no need in keeping the contents.
66 \item \texttt{vector} - Pointer to vector to add the pair to. Declare a key-value vector with the 'PICO$\_$DNS$\_$SD$\_$KV$\_$VECTOR$\_$DECLARE'-macro.
H A Dchap_api_mdns.tex4 This module can register DNS resource records on the network via Multicast DNS as either \textbf{\emph{shared}} or \textbf{\emph{unique}} records. Unique records are, as the name implies, unique on the network (the record-name and -type combination is unique) and one single host has claimed the ownership of them. Shared records are records that are not unique on the network, which means multiple hosts can register records with the same record-name and -type combination. For more information on shared and unique resource record sets, see RFC6762.
114 \item \texttt{record$\_$tree} - mDNS record-tree with records to register on the network via Multicast DNS. Can contain \textbf{\emph{unique records}} as well as \textbf{\emph{shared records}}. Declare a mDNS record-tree with the macro 'PICO$\_$MDNS$\_$RTREE$\_$DECLARE(name)', which is actually just a pico$\_$tree-struct, with a comparing-function already set. Records can be added with the preprocessor macro 'PICO$\_$MDNS$\_$RTREE$\_$ADD(pico$\_$mdns$\_$rtree *, struct pico$\_$mdns$\_$record *)'. To create mDNS records see 'pico$\_$mdns$\_$record$\_$create'.
151 \item \texttt{url} - URL of the DNS name to query records for.
152 \item \texttt{type} - DNS type of the records to query for on the network.
189 \item \texttt{url} - DNS resource record name in URL format. Will be converted to DNS name notation format.
190 \item \texttt{$\_$rdata} - Memory buffer with data to insert in the resource record. If data of record should contain a DNS name, the name in the databuffer needs to be in URL-format.
191 \item \texttt{datalen} - The exact length in bytes of the $\_$rdata-buffer. If data of record should contain a DNS name (f.e. with PICO$\_$DNS
[all...]
H A Dchap_api_dns_c.tex1 \section{DNS client}
24 \item \texttt{PICO$\_$DNS$\_$NS$\_$ADD} - to add a nameserver
25 \item \texttt{PICO$\_$DNS$\_$NS$\_$DEL} - to remove a nameserver
H A Dchap_api_sntp_c.tex11 Function to sync the local time to a given sntp server in string notation. DNS resolution will be done automatically.
31 \item \texttt{PICO$\_$ERR$\_$EPROTONOSUPPORT} - compiled without DNS support
H A Dchap_api_dhcp_c.tex161 \item \texttt{struct pico\_ip4} - the address of the nameserver that should be used. On failure, e.g. an invalid index was passed, it returns "255.255.255.255". If the IP address of the DNS has not been set, it may return INADDR\_ANY.
/seL4-camkes-master/projects/util_libs/libethdrivers/src/plat/zynq7000/uboot/
H A Dnet.h527 BOOTP, RARP, ARP, TFTPGET, DHCP, PING, DNS, NFS, CDP, NETCONS, SNTP, enumerator in enum:proto_t
/seL4-camkes-master/projects/util_libs/libethdrivers/src/plat/tx2/uboot/
H A Dnet.h535 BOOTP, RARP, ARP, TFTPGET, DHCP, PING, DNS, NFS, CDP, NETCONS, SNTP, enumerator in enum:proto_t

Completed in 106 milliseconds