DNS resolving in network namespace works partially

Hello, I have a service that does the following: create network namespace called “connect” move eth1 to this namespace (to be used as LAN interface) creates Wireguard connection in main namespace, then moves it to “connect”. This Wireguard connection has default route via it. (to be used as WAN) All good, but resolving in the namespace work partially. For example, nslookup google.com returns results, but curl google.com says the address can’t be resolved. ping can’t resolve as well. If I cur...