Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752432AbdHIE7Y (ORCPT ); Wed, 9 Aug 2017 00:59:24 -0400 Received: from gherkin.frus.com ([192.158.254.49]:39614 "EHLO gherkin.frus.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbdHIE7X (ORCPT ); Wed, 9 Aug 2017 00:59:23 -0400 X-Greylist: delayed 1914 seconds by postgrey-1.27 at vger.kernel.org; Wed, 09 Aug 2017 00:59:23 EDT Date: Tue, 8 Aug 2017 23:27:16 -0500 From: Bob Tracy To: linux-kernel@vger.kernel.org Subject: [BUG] resolver strangeness in 4.12 Message-ID: <20170809042716.GA4868@gherkin.frus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 519 Lines: 12 No idea where to begin tracking this down :-(. After approximately six days of uptime with a 4.12.0 kernel, the DNS resolver simply quits working. All query attempts come back with "no DNS servers can be reached". External hosts can still query the BIND server running on the host with the non-functional resolver. Restarting "named" has no effect. Rebooting the machine restores functionality. So far, this is completely reproducible. Everything worked fine with 4.11.0. Going to try a 4.13-rc4 kernel. --Bob