On Sat, 21 Oct 2023 14:40:49 -0400 Pocket <poc...@columbus.rr.com> wrote:
> but the machine in question has > bind running so nameserver needs to be set to 127.0.0.1 and the > domain to example.org in the resolv.conf file. > > This is my problem in a nutshell Oh, why didn't you say that! Actually, it doesn't have to use the loopback address; you can use the address of the Ethernet interface. Also, you should not be using example.org. That is a reserved domain name. https://en.wikipedia.org/wiki/Example.com I am going to guess (since you haven't said so) that this is also not a laptop, and therefor it has a permanent IP address. If you insist on retaining NetworkManager, this page might be useful. https://serverfault.com/questions/810636/how-to-manage-dns-in-networkmanager-via-console-nmcli You can also add DNS servers in the GTK version of the NM GUI. I don't know about the KDE version. You can use isc-dhcp to tell the whole network where its DNS server is. You can also make over-rides for individual hosts. In dhcpd.conf: subnet blah { option domain-name-servers blah, blah; option domain-search etc.; host dns-server { option domain-name-servers 192.168.100.30, 127.0.0.1; } } You said in another email that you are using a dhcp server on a "router". That doesn't tell me much. A router is simply a computer that sits between two networks, and routes packets between them. My router is a 16 year old computer designed for embedded applications that runs Debian. I run ISC DHCPD on that an another machine with fail-over between them. From what I have seen most "routers" these days are cheap boxes provided by ISPs that have buggy, insecure, and limited software which may not be able to do this. You can also set the ISC dhcp client to add name servers. prepend domain-name-servers 127.0.0.1; -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
