o1bigtenor via Dng said on Mon, 28 Aug 2023 08:49:47 -0500

>On Mon, Aug 28, 2023 at 1:36 AM al3xu5 <dotcommon@???> wrote:

>> https://troubleshooters.com/linux/unbound_nsd/unbound.htm
>>
>
>Hmmmmmm - - - - wha'ts not clear is - - - - does this mean that every
>computer on
>my network has to have this 'unbound' running?
>
>Please advise.
>
>(I'm looking for a solution for my network - - - - not just one
>computer.)

If your network is a fast and reliable LAN rather than a WAN, then the
ideal situation is to have one copy of Unbound running on the LAN, so
requests from all the LAN's computers are cached for all to quickly
retrieve. The computer running Unbound would have to run 24/7.

You'll need to have Unbound operating on an Ethernet alias of the
computer hosting it, and that IP adddress must remain constant. For
instance, my Daily Driver Desktop (DDD) operates on 192.168.0.2, with
an alias of 192.168.0.102 for Unbound to run on. Therefore, anywhere on
my LAN, a computer's /etc/resolve.conf can be set to 192.168.0.102 to
obtain quick DNS query results.

I'd suggest that laptops you use outside the LAN have their own Unbound
so they are useable outside your headquarters, like at the coffee shop
etc. However, if they're used *mostly* at headquarters, you could
install Unbound on them, and put the LAN's Unbound DNS recursive
resolver first in /etc/resolv.conf. Then, when you travel, comment out
the LAN's unbound so queries to your LAN DNS don't time out before
going to a public DNS.

Remember:

chattr -i resolv.conf; vim resolv.conf; chattr +i resolv.conf

The preceding command, when done with a CLI editor that runs in the
foreground, minimizes the chance of a race condition with those
"helpful" apps that change resolv.conf.

HTH,


SteveT