diff options
| author | Petr Spacek <pspacek@redhat.com> | 2016-08-11 13:44:29 +0200 |
|---|---|---|
| committer | Martin Basti <mbasti@redhat.com> | 2016-08-16 14:23:30 +0200 |
| commit | f2fe35721967531257bc952b766a7c77e71be826 (patch) | |
| tree | d5f489d3da0dff49049aa74633918f371435d38e /ipapython/ipavalidate.py | |
| parent | 64c5340329b8eeaf7d8995a3c86b9bdf10ea9252 (diff) | |
| download | freeipa-f2fe35721967531257bc952b766a7c77e71be826.tar.gz freeipa-f2fe35721967531257bc952b766a7c77e71be826.tar.xz freeipa-f2fe35721967531257bc952b766a7c77e71be826.zip | |
DNS server upgrade: do not fail when DNS server did not respond
Previously, update_dnsforward_emptyzones failed with an exeception if
DNS query failed for some reason. Now the error is logged and upgrade
continues.
I assume that this is okay because the DNS query is used as heuristics
of last resort in the upgrade logic and failure to do so should not have
catastrophics consequences: In the worst case, the admin needs to
manually change forwarding policy from 'first' to 'only'.
In the end I have decided not to auto-start BIND because BIND depends on
GSSAPI for authentication, which in turn depends on KDC ... Alternative
like reconfiguring BIND to use LDAPI+EXTERNAL and reconfiguring DS to
accept LDAP external bind from named user are too complicated.
https://fedorahosted.org/freeipa/ticket/6205
Reviewed-By: Martin Basti <mbasti@redhat.com>
Diffstat (limited to 'ipapython/ipavalidate.py')
0 files changed, 0 insertions, 0 deletions
