June 15, 20224 yr I had my DNS set to my routers IP or the adguard container's IP (which had its own IP) in Unraid's network settings. Everything was working as intended. When I rebooted after the update, Unraid itself did not have DNS (for example I could not ping google.com) and neither did the containers. I had to set my DNS in network settings to 8.8.8.8 to resolve. The problem is now I cannot use my split DNS within my containers. Is there a reason why I cannot set my DNS to a container on Unraid? Or why this was working but stopped? The other day when I tried to unsuccessfully setup wireguard, all my containers went down on uptime kuma running on a pi. I don't know if that could be related. This was resolved after disabling the wireguard network. Edit: I think this has something to do with wireguard. After the reboot, the wireguard network was active. I could not ping my router. I got some error and reference to the wireguard network. I guess I have kind of solved my issue: just don't use wireguard. But I am curious what is actually happening here? Edited June 15, 20224 yr by 54lzy
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.