Re: Solved Re: debian 13 - no virtual machines
On Wednesday, 1 October 2025 04:11:46 -03 Michael wrote:
> On 9/29/25 21:21, Charles Curley wrote:
> > On Mon, 29 Sep 2025 19:27:04 +0200
> >
> > Michael <dpweb01@web.de> wrote:
> >> 1. How can I achieve that bind is not started? If I kill the
> >> process
> >> "/usr/sbin/named -f -u bind" with "kill -9 1227", it is
> >> immediately restarted with a different process ID.
> >
> > Use the standard systemctl commands to stop it, disable it, and mask
> > it. Or do as Greg Wollege suggested, and remove it.
> >
> >> 2. Charles, in your proposal for adding to named.conf, what is the
> >> IP
> >> "192.168.100.6"? Shall I replace it with the static IP of my
> >> computer?>
> > Sorry I wasn't clear there. Yes, that is your computer's
> > ethernet/WiFi IP address.
> >
> >> 3. I never did any changes to the default startup- and network
> >> procedures in Debian. Why does the installation start both bind and
> >> dnsmasq?
> >
> > Because the people packaging them know *nothing* about what you are
> > up to. They assume (not unreasonably) that if you install their
> > package you must want to run it. but beyond that they neither know
> > nor assume anything.
> >
> > The libvert packages require dnsmasq, so if you are running virtual
> > machines, that's how you got dnsmasq. I have no idea why you have
> > bind9 installed.
>
> Hallo,
>
> the problem is solved. For those interested a short summary:
>
> A year ago I tried to run pihole on my laptop. I found a tutorial and
> followed the steps described there and run a shell script. This script
> installed some programs and config files.
>
> a) After deleting the package bind9 (see the hint above) and only
> dnsmasq was running, the error still occured.
>
> b) It turned out that dnsmasq was started by init.d (you see I had
> migrated Debian several times to a newer version :-).
>
> I could stop the start of dnsmasq with "update-rc.d dnsmasq
> disable"
>
> c) However the error still occured. I then deleted all programs and
> config files related to pihole. Now it works!
>
>
> Summary: I guess I should better install a fresh Debian and get rid of
> all old stuff which results from earlier tests and several old debian
> versions ;-)
>
> Thanks again for your help,
>
> Michael
Hi Michael,
you will be better off with Pi-Hole on a dedicated RaspberryPi and stick
with the default install of that s/w package - I think.
All the best
--
Eike Lantzsch KY4PZ / ZP5CGE
Reply to: