Greg Wooledge <g...@wooledge.org> wrote: > On Thu, Oct 24, 2024 at 20:16:30 +0100, Chris Green wrote: > > It works fine though. The /etc/resolv.conf is:- > > > > domain zbmc.eu > > search zbmc.eu > > nameserver 192.168.1.1 > > > > which simply means all DNS gets passed to my LAN's DNS server. Is that > > what one gets on a minimal installation, no explicit DNS server or > > resolv management? I'm very happy with this, it's very simple and the > > backup system isn't going to make a lot of DNS queries such that it > > needs a DNS cache. Have I understood this OK? > > In a typical installation, on a typical network, you will get your DNS > configuration via DHCP, from whatever is acting as your network's DHCP > server. In your case, I'm guessing it's a router. > > Check the /etc/network/interfaces file and see if you have your interface > configured for dhcp. I'm guessing you do. > > With DNS configuration being provided by DHCP, any changes you make to > the /etc/resolv.conf file will be overwritten every time the DHCP client > daemon renews its DHCP lease. This will usually happen once or twice > per day. > > If you'd like to set up a local caching DNS nameserver, then you'll need > to work out a way to change your resolv.conf file without your changes > being overwritten. There are many different approaches to this. > > See <https://wiki.debian.org/resolv.conf> to see some ways of doing it.
Ah, thank you, that link to the wiki tells me what I need to know. -- Chris Green ยท
