Date: Mon, 21 Aug 2017 13:17:02 +0200 From: Bert Kiers <kiersb@xs4all.net> To: Victor Sudakov <vas@mpeks.tomsk.su> Cc: freebsd-net@freebsd.org Subject: Re: resolv.conf and a non-standard port Message-ID: <569ac975-0f5c-131a-a236-67cff377ef6c@xs4all.net> In-Reply-To: <20170821110400.GA45463@admin.sibptus.transneft.ru> References: <20170821102354.GA44676@admin.sibptus.transneft.ru> <5e2bb578-a9c7-93fa-f144-d0a4302cb28c@xs4all.net> <20170821110400.GA45463@admin.sibptus.transneft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21/08/2017 13:04, Victor Sudakov wrote: > Bert Kiers wrote: >> >>> How can I configure the resolver to use a DNS server with a >>> non-standard port? >>> >>> I have a host running an authoritative-only server (nsd) for the >>> world, and I want to run local unbound for the host itself (can't use >>> nsd for recursive queries). >>> >>> Unbound can listen on a non-standard port, but how do I configure the >>> host to use the DNS server at 127.0.0.1:5353 ? >> >> I think it will be more simple to have nsd and unbound listen on >> different IP-adresses, like unbound on 127.0.0.1 and nsd on the external >> IP-address. Then put 127.0.0.1 in resolv.conf > > That's how I have configured it now, but this solution has a major > drawback: you need to specify the IP address explicitely in > /var/unbound/unbound.conf which can be inconvenient in some > situations. > > So it's a workaround, but by no means "more simple." What happens when you let unbound listen on 127.0.0.1 and nsd on * (a.k.a. 0.0.0.0)? That may work because 127.0.0.1 is more specific. Maybe the startup order of the daemons is important then. -- Bert Kiers, suspected terrorist Love MS-Windows? Must be Stockholm syndrome.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?569ac975-0f5c-131a-a236-67cff377ef6c>