From owner-freebsd-current@FreeBSD.ORG Fri Jan 30 22:25:20 2015 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A391D86F for ; Fri, 30 Jan 2015 22:25:20 +0000 (UTC) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 66B30FAF for ; Fri, 30 Jan 2015 22:25:20 +0000 (UTC) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id E28903B8B7 for ; Fri, 30 Jan 2015 22:25:11 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id t0UMOoiW002534 for ; Fri, 30 Jan 2015 22:25:09 GMT (envelope-from phk@phk.freebsd.dk) To: current@freebsd.org Subject: Bug-report of sorts... From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2500.1422656498.1@critter.freebsd.dk> Date: Fri, 30 Jan 2015 22:24:50 +0000 Message-ID: <2533.1422656690@critter.freebsd.dk> X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jan 2015 22:25:20 -0000 I'm at a hotel in Bruxelles right now, and the cordially provided free wireless is a lot less useful than it can be, because my FreeBSD box can't seem to do DNS lookups on it. It's one of those "captive portal" kind of things where you get a DHCP reply with a DNS server which lies to you until you agree to the T&C on a web-page. But the point is I never get to the webpage, local_unbound just doesn't seem to be able to resolve anything through the DHCP appointed server, despite the fact that dig(1) does so just fine. I have no idea what goes wrong or why it goes wrong, local_unbound does not seem to record anything in syslog about failures. I'm here for a couple of days (as are, I belive, another couple of FreeBSD people) in case anybody has any ideas to try... Input welcome... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.