From owner-freebsd-questions@FreeBSD.ORG Fri Sep 27 22:08:48 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CA9349D4 for ; Fri, 27 Sep 2013 22:08:48 +0000 (UTC) (envelope-from terje@elde.net) Received: from keepquiet.net (keepquiet.net [78.46.162.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 89EDF2DCF for ; Fri, 27 Sep 2013 22:08:48 +0000 (UTC) Received: from [10.130.11.108] (cm-84.210.76.250.getinternet.no [84.210.76.250]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: terje@elde.net) by keepquiet.net (Postfix) with ESMTPSA id 3840F2E443; Sat, 28 Sep 2013 00:08:46 +0200 (CEST) References: <5245CC59.5060204@laposte.net> <524600CF.3040609@fjl.co.uk> In-Reply-To: <524600CF.3040609@fjl.co.uk> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <13463C66-C15D-48E0-B926-CA0BF6580CAD@elde.net> X-Mailer: iPhone Mail (10B329) From: Terje Elde Subject: Re: How to ask a DNS resolver listening on a different port than the tcp/udp 53 Date: Sat, 28 Sep 2013 00:08:46 +0200 To: Frank Leonhardt Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Sep 2013 22:08:48 -0000 On 28. sep. 2013, at 00:03, Frank Leonhardt wrote: > If I understand the way it works correctly, the resolver pulls a list of t= he NS and hard-sets the port number for each to 53 (via a manifest constant)= . See libc/resolv/res_init.c. All you need to do(!) is change this to a val= ue of your choice and recompile libc Sorry, but this is startin to look a lot like a complicated solution to a pr= oblem that isn't really there... Why not just point from resolv.conf to localhost, run a caching and/or recur= sive dns-server there, and point it whereever? As far as I can tell, that'd solve everything, add caching, and let it all b= e controlled from the config of the DNS-server? Terje