Built in DHCP Server is giving wrong DNS Server to requesting clients

I have found an error. I have enabled the DHCP server and have ipv6 addresses assigned from fd00::2 to ff. My raspberry has

a private ip(v4) adress like 192.168.x.x
and also a fd00 ipv6 adress
and also a fe80 adress
and also an public 2003:: adress with a given prefix from the internet router/gateway.

Till here the build in DHCP Server is working fine and giving ipv6 IPs ranged from fd00:2 to ff to asking clients. The DHCP Server also gives the its own DNS adresses to the requesting clients.

But now I limited the AdGuard DNS Server to listen only at 192.168.x.2 and fd00::2. Because I don't want it to listen for dns queries at the public reachable 2003:x.x... and the link local fe80 adresses. This is done in AdGuardHome.yaml like that:

'dns:
' - 192.168.178.2
' - fd00:2
That works fine and in the webIf at the tab "Setup Guide" I see also, that adguard home's dns server is working now only with that ip adresses, like you see in my attached screenshot:

But now the problem is, that the DHCP Server is still giving the other adresses to the requesting clients. So the clients getting additionaly that public 2003:: and that fe80: adresses. I think that is wrong and the build in dhcp server should only give the 2 adresses the dns is limited to via config.
Because of this, it happens that clients have now wrong DNS server adresses. What is causing dns timeouts at clients and a not working internet.
How can I make that build in dhcp server to give only that 2 adresses to clients?