Hoi Arnold, Be aware that in most configurations /etc/resolv.conf is (re)created at boot time on configuration of the nic. If the nic is configured through dhcp, check there for the weird ip address! If it is configured otherwise, check there. It might be that the stub file is not overwritten at boot.
Saturday, May 10, 2025, 2:40:30 PM, you wrote: > > On 2025-05-10 02:03, Greg Choules wrote: > > > > > @Danilo you are correct, the contents of /etc/resolv.conf are not > set by BIND and BIND itself does not use them. But all applications > running on that machine (including dig, unless you specify > @<address>) that want some kind of name resolution will make OS > system calls and then the OS *will* use what's in resolv.conf to > determine where to send DNS queries on behalf of the application. > > Therefore, I will change resolv.conf to replace the current IP with > the IP of the server machine itself and, perhaps, Localhost itself > (127.0.0.1). I never created resolv.conf and have no idea how it got > created. It's weird because "/etc/resolv.conf" is actally a symlink > to /run/systemd/resolve/stub-resolv.conf"... the file I need to change. > <snip> Tot mails, bind userlist mailto:bind-users@lists.isc.org "Zonder hoop kun je niet leven Zonder leven is er geen hoop Het eeuwige dilemma Zeker als je hoop moet vernietigen om te kunnen overleven!" De lerende Mens -- -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
