MIME-Version: 1.0 In-Reply-To: <53721630.9010708@redhat.com> X-Mailer: MIME-tools 5.428 (Entity 5.428) Content-Disposition: inline References: <53721630.9010708@redhat.com> Content-Type: text/html; charset="UTF-8" Message-ID: Content-Transfer-Encoding: binary X-RT-Original-Encoding: utf-8 RT-Send-CC: Content-Length: 2139  
I've queue up a patch for 4.3.1 first that is awaiting review it has the
dhcp process continue running even if it the code can't handle resolv.conf.

diff --git a/omapip/isclib.c b/omapip/isclib.c
index 59332ed..ce6d505 100644
--- a/omapip/isclib.c
+++ b/omapip/isclib.c
@@ -225,9 +225,17 @@ dhcp_context_create(int flags,
                if (result != ISC_R_SUCCESS)
                        goto cleanup;
 
+               /*
+                * If we can't set up the servers we may not be able to
+                * do DDNS but we should continue to try and perform
+                * our basic functions and let the user sort it out.
+                */
                result = dhcp_dns_client_setservers();
-               if (result != ISC_R_SUCCESS)
-                       goto cleanup;
+               if (result != ISC_R_SUCCESS) {
+                       log_error("Unable to set resolver from resolv.conf "
+                                 "continuing to start up but DDNS support "
+                                 "may be affected");
+               }
        }
 #endif