If the user runs ipa-client, attempt autodiscovery. If autodiscovery fails, the first thing ipa-clinet should do is get the name or IP address of the nameserver, update resolve.conf, and then retry autodiscovery. If it fails again, it then tests for firewall ports etc. If it attempts to do an xmlrpc to the IPA server, get back a "Negotiate" response, and yet it can't talk to the KDC, it is likely a firewall issue, and should report as such. These are probably the most common issues on client install.
If the client install is canceled, return resolv.conf back to its original values.
Rename component.
Metadata Update from @admiyo: - Issue assigned to rcritten - Issue set to the milestone: Tickets Deferred
In the era of systemd-resolvd and NetworkManager one of which by default generally owns resolv.conf if we twiddle with it during installation its likely to either be overwritten or will break something which will in turn break the system.
This would be pretty user-friendly to be able to help the end-user figure out their network issues but may just add complexity and problems like "my client suddenly can't resolve the server anymore".
Closing as wontfix.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.