summaryrefslogtreecommitdiff
path: root/src/resolv/async_resolv.h
AgeCommit message (Collapse)AuthorFilesLines
2013-09-05resolv_sort_srv_reply: remove unnecessary mem_ctxPavel Březina1-1/+1
2013-07-23Remove unused constant.Michal Zidek1-2/+0
2013-05-07Actually use the index parameter in resolv_get_sockaddr_address_indexJakub Hrozek1-2/+3
2013-05-03dyndns: New option dyndns_update_ptrJakub Hrozek1-2/+5
https://fedorahosted.org/sssd/ticket/1832 While some servers, such as FreeIPA allow the PTR record to be synchronized when the forward record is updated, other servers, including Active Directory, require that the PTR record is synchronized manually. This patch adds a new option, dyndns_update_ptr that automatically generates appropriate DNS update message for updating the reverse zone. This option is off by default in the IPA provider. Also renames be_nsupdate_create_msg to be_nsupdate_create_fwd_msg
2013-05-03resolver: Return PTR record as stringJakub Hrozek1-0/+4
This is a requirement to update the PTR records. Includes a unit test.
2013-04-10resolv: add resolv_discover_srv request to resolv utilsPavel Březina1-0/+13
2013-04-10resolv: add resolv_get_domain request to resolv utilsPavel Březina1-0/+14
2013-04-03Centralize resolv_init, remove resolv context listJakub Hrozek1-1/+1
2013-04-03Init failover with be_res optionsJakub Hrozek1-5/+0
2011-07-11Allow returning arbitrary address from resolv_hostent as stringJakub Hrozek1-1/+6
2011-07-11Split reading resolver family order into a separate functionJakub Hrozek1-0/+8
2011-07-11Do not hardcode default resolver timeoutJakub Hrozek1-0/+2
2011-06-30Add sockaddr_storage to sdap_serviceSumit Bose1-0/+4
2011-06-15Switch resolver to using resolv_hostent and honor TTLJakub Hrozek1-25/+31
2011-06-15Add new resolv_hostent data structure and utility functionsJakub Hrozek1-0/+29
2011-06-02Add utility function to return IP address as stringJakub Hrozek1-0/+3
2010-04-30Sort SRV replies according to RFC 2782Jakub Hrozek1-0/+4
RFC 2782 defines a way to sort replies to a SRV query. In short, the algorithm sorts all replies by priority and then does a weight-based selection for every priority level. For details, please see the sections "Usage rules" for overview of the algorithm and section "The 'Weight' field" for description on the weight selection.
2010-02-22Restrict family lookupsJakub Hrozek1-1/+9
Adds a new option that tells resolver which address family to prefer or use exclusively. Fixes: #404
2010-02-18Rename server/ directory to src/Stephen Gallagher1-0/+95
Also update BUILD.txt