summaryrefslogtreecommitdiffstats
path: root/src/providers/ipa/ipa_dyndns.c
Commit message (Collapse)AuthorAgeFilesLines
* Check whether servername is not empty string.Lukas Slebodnik2013-08-191-1/+1
| | | | Previous check was wrong, servername cannot be NULL.
* Fix dyndns timer initializationJakub Hrozek2013-05-271-0/+7
| | | | | | | The dyndns init function was starting the timer even if the updates were set to False. This patch splits the init of dynamic updates and the timer into two functions so that the back end can start the updates separately from reading the options.
* Split out the common code from timed DNS updatesJakub Hrozek2013-05-031-60/+12
|
* dyndns: new option dyndns_authJakub Hrozek2013-05-031-0/+1
| | | | | | This options is mostly provided for future expansion. Currently it is undocumented and both IPA and AD dynamic DNS updates default to GSS-TSIG. Allowed values are GSS-TSIG and none.
* dyndns: New option dyndns_update_ptrJakub Hrozek2013-05-031-1/+3
| | | | | | | | | | | | | | | | 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
* dyndns: new option dyndns_refresh_intervalJakub Hrozek2013-05-031-0/+107
| | | | | | | This new options adds the possibility of updating the DNS entries periodically regardless if they have changed or not. This feature will be useful mainly in AD environments where the Windows clients periodically update their DNS records.
* Convert IPA-specific options to be back-end agnosticJakub Hrozek2013-05-031-4/+5
| | | | | | This patch introduces new options for dynamic DNS updates that are not specific to any back end. The current ipa dyndns options are still usable, just with a deprecation warning.
* Refactor dynamic DNS updatesJakub Hrozek2013-05-031-1163/+74
| | | | | | | | | | | | Provides two new layers instead of the previous IPA specific layer: 1) dp_dyndns.c -- a very generic dyndns layer on the DP level. Its purpose it to make it possible for any back end to use dynamic DNS updates. 2) sdap_dyndns.c -- a wrapper around dp_dyndns.c that utilizes some LDAP-specific features like autodetecting the address from the LDAP connection. Also converts the dyndns code to new specific error codes.
* dyndns: Fix initializing sdap_id_ctxJakub Hrozek2013-04-041-1/+1
|
* Centralize resolv_init, remove resolv context listJakub Hrozek2013-04-031-8/+1
|
* Init failover with be_res optionsJakub Hrozek2013-04-031-20/+7
|
* Filter out multicast addresses from IPA DNS updatesJakub Hrozek2013-02-121-1/+1
| | | | https://fedorahosted.org/sssd/ticket/1804
* IPA: Handle bad results from c-ares lookupStephen Gallagher2012-12-021-1/+11
| | | | | | | | | In some situations, the c-ares lookup can return NULL instead of a list of addresses. In this situation, we need to avoid dereferencing NULL. This patch adds a log message and sets the count to zero so it is handled appropriately below.
* Make TTL configurable for dynamic dns updatesJames Hogarth2012-10-161-2/+12
|
* Filter out IP addresses inappropriate for DNS forward recordsJakub Hrozek2012-05-101-1/+57
| | | | https://fedorahosted.org/sssd/ticket/949
* execv, excvp and exec_child never return EOKStef Walter2012-05-011-5/+3
| | | | * So don't need to handle that case
* Return correct resolv_status on resolver timeoutJakub Hrozek2012-03-291-1/+6
| | | | https://fedorahosted.org/sssd/ticket/1274
* Save errno value before calling DEBUGJakub Hrozek2012-02-231-2/+4
|
* Don't give memory context in confdb where not neededJan Zeleny2012-02-211-1/+1
|
* IPA: Detect nsupdate support for the realm directiveStephen Gallagher2012-01-171-14/+40
| | | | | For older platforms, do not add the 'realm' line in the update message
* Move child_common routines to utilStephen Gallagher2011-12-191-1/+1
|
* New IPA ID contextJan Zeleny2011-11-231-8/+10
|
* Cleanup: Remove unused parametersJakub Hrozek2011-11-221-2/+1
|
* IPA dyndns: do not segfault if the server cannot be resolvedJakub Hrozek2011-08-251-4/+2
| | | | https://fedorahosted.org/sssd/ticket/963
* Remove incorrect private variableStephen Gallagher2011-08-011-1/+1
| | | | | | This caused no ill effects, since it wasn't used in the callback. However, it is a layering violation (especially since req is freed in the callback)
* Check DNS records before updatingJakub Hrozek2011-07-111-21/+463
| | | | https://fedorahosted.org/sssd/ticket/802
* ipa_dyndns: Use sockaddr_storage for storing IP addressesJakub Hrozek2011-07-051-12/+17
| | | | https://fedorahosted.org/sssd/ticket/915
* Log nsupdate messageJakub Hrozek2011-06-211-0/+3
| | | | https://fedorahosted.org/sssd/ticket/893
* Fixes for dynamic DNS updateSumit Bose2011-03-031-16/+87
| | | | | | | | | | | | | | The current code assumed that only one server is given in the ipa_server config option and fails if multiple servers were given. To fix this nsupdate is first called without a server name assuming that nsupdate is able to find the name of the master DNS server of the zone by reading the SOA record. If this fails the IP address of the currently active LDAP server is used and nsupdate is called again. If there is no default realm given in /etc/krb5.conf nsupdate start trying to find a realm based on the DNS domain which might lead to wrong results. To be on the safe side the realm was added to the message send to nsupdate.
* Use new LDAP connection framework in IPA dynamic DNS forwarder.eindenbom2010-07-091-38/+122
|
* Remove signal event if child was terminated by a signalSumit Bose2010-05-271-1/+8
|
* Add dynamic DNS updates to FreeIPAStephen Gallagher2010-05-161-0/+580
| | | | | | | | | | | | | | | | | | This adds two new options: ipa_dyndns_update: Boolean value to select whether this client should automatically update its IP address in FreeIPA DNS. ipa_dyndns_iface: Choose an interface manually to use for updating dynamic DNS. Default is to use the interface associated with the LDAP connection to FreeIPA. This patch supports A and AAAA records. It relies on the presence of the nsupdate tool from the bind-utils package to perform the actual update step. The location of this utility is set at build time, but its availability is determined at runtime (so clients that do not require dynamic update capability do not need to meet this dependency).
* Revert "Add dynamic DNS updates to FreeIPA"Stephen Gallagher2010-05-071-580/+0
| | | | | | | This reverts commit 973b7c27c0b294b8b2f120296f64c6a3a36e44b7. While this patch applied cleanly, it was uncompilable. Reverting until it can be properly merged.
* Add dynamic DNS updates to FreeIPAStephen Gallagher2010-05-071-0/+580
This adds two new options: ipa_dyndns_update: Boolean value to select whether this client should automatically update its IP address in FreeIPA DNS. ipa_dyndns_iface: Choose an interface manually to use for updating dynamic DNS. Default is to use the interface associated with the LDAP connection to FreeIPA. This patch supports A and AAAA records. It relies on the presence of the nsupdate tool from the bind-utils package to perform the actual update step. The location of this utility is set at build time, but its availability is determined at runtime (so clients that do not require dynamic update capability do not need to meet this dependency).
generated by cgit (git 2.34.1) at 2024-04-28 14:29:22 +0000