zephyr

History

Flavio Santes 44b2f212a1 iot/dns: Use a k_sem for the DNS rx routine This patch introduces a k_sem that will block until: - data is received, or - the user-provided timeout expires This change allows us to simplify our previous DNS client implementation. This change is related to ZEP-1357 because we are refactoring the DNS client API removing the continuous update of the net_context_recv routine that seems to be causing issues after the kernel's update. Jira: ZEP-1357 Change-Id: If01c9274ac8f096f0095a2872f86be2e007212ee Signed-off-by: Flavio Santes <flavio.santes@intel.com>		2016-12-16 19:14:53 +01:00
..
Kconfig	…
Makefile	…
README	…
dns_client.c	iot/dns: Use a k_sem for the DNS rx routine	2016-12-16 19:14:53 +01:00
dns_pack.c	iot/dns: Introduce the dns_context structure	2016-12-16 19:14:52 +01:00
dns_pack.h	iot/dns: Introduce the dns_context structure	2016-12-16 19:14:52 +01:00

README

DNS Client API for Zephyr
=========================


Known limitations:

- Synchronous queries
- Only IPv4 and IPv6 records can be handled
- Minimal protocol validation. If you do not trust your DNS server,
  it is time to change it :)


Usage:

Before calling the resolver, it must be initialized via the 'dns_init'
routine.

'dnsX_resolve_quick' routines just return the first IP address.
However, domain names may be served by more IP addresses, so
'dnsX_resolve' routines may be more useful.

See samples/net/dns_client/src/main.c.