Wow, thanks!! That actually solved it apparently! Why does the wireguard config change if i can ping outside the docker container though? Is it because the wireguard client inside the container opens up ip adresses or something? :) Thanks again! Itried to find a solution for many hours yesterday :D

Oh and is the ‘,’ in the allowed ips meant as an “and” or rather an “or”?

When I am on the server, it can even ping the domain. On my laptop, it can only resolve the domain to the correct ip

Changing the domain does not change the problem sadly. I thought .local is a safe one to use

So in the dnsmasq.config file is this entry: ‘address=/server.local/192.168.178.10’ and using nslookup it resolves it correctly