Date: Sat, 20 Sep 2025 16:56:21 +0300 From: Vadim Goncharov <vadimnuclight@gmail.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Andriy Gapon <avg@FreeBSD.org>, "net@FreeBSD.org" <net@FreeBSD.org> Subject: Re: DHCP on multi-homed host, some thoughts Message-ID: <20250920165621.25009928@nuclight.lan> In-Reply-To: <sr41p98p-q26p-28rs-33r0-528s05p481q3@yvfgf.mnoonqbm.arg> References: <6abe9da1-9818-438b-ad8f-5424e50a39ce@FreeBSD.org> <sr41p98p-q26p-28rs-33r0-528s05p481q3@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 20 Sep 2025 07:06:56 +0000 (UTC) "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> wrote: > But chosing an upstream DNS with the wrong source address often won't > work. At least here ISPs won't allow you to use their resolver if you > are not coming from their IP range. > The answer then really is to run a local resolver independent on > upstream for as long as that is feasible and working (*). [...] > (*) and before anyone suggests any of the open resolvers which collect > your data, please leave this thread alone. This way, while works, is not very good for Internet as a whole, and top-level DNS servers in particular, due to increased number of requests because of caches in the network are not utilized; and increased latency for user. And who will pay for this? Not that I'm advocating for N.N.N.N collectors but they, like ISP resolvers, don't have this problem. -- WBR, @nuclight
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20250920165621.25009928>