DNS not starting after update to Bullseye

Please follow the below template, it will help us to help you!

Expected Behaviour:

-Raspbian Bullseye

Actual Behaviour:

had installed under raspbian Buster Phiole in the version before the current release of PiHole. After updating to Raspbian Bullseye, PiHole could no longer be started.
Also the new installation of the current release of PiHole did not solve the problem.
On the webinterface it says NDS not running and FTL can't be started either.
I have seen that by updating to Raspbian Bullseye Bein connmand the DNS proxy service is also started. So port 53 is occupied by another service. If I uninstall connmand all network interfaces are disabled.
Can someone tell me how I can start connmand permanently without DNS proxy or is this a bug in PiHole because when installing it does not check if connmand is installed and has the DNS proxy enabled.

Debug Token:

https://tricorder.pi-hole.net/QBnBMBK8/

You have other services running on ports used by Pi-hole, and this is the cause of your problems. Port 53 is needed by pihole-FTL and port 80 is used by lighttpd. If you weren't running connmand prior to Bullseye, something in your upgrade process installed it. I would visit the forums for your OS and find out how to disable this.

*** [ DIAGNOSING ]: Ports in use
[53] is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)

[80] is in use by apache2 (https://docs.pi-hole.net/main/prerequisites/#ports)
*:443 apache2 (IPv6)

*** [ DIAGNOSING ]: Pi-hole diagnosis messages
   id    timestamp            type                  message                                                                blob1                 blob2                 blob3                 blob4                 blob5               
   ----  -------------------  --------------------  ---------------------------------------------------------------------  --------------------  --------------------  --------------------  --------------------  --------------------
   1     2021-09-13 20:32:41  DNSMASQ_CONFIG        failed to create listening socket for port 53: Address already in use

I don't think this is a bug. We support a wide variety of OS's, and any number of other processes can be running that interfere with Pi-hole.

I will note that I am running several instances of Raspbian Bullseye and have not encountered any conflicts on port 53.