I have pihole running as a VM hosted on truenas. When I try to have truenas connect to pihole as a DNS I can’t see any logs in pi hole where trunas has even tried to connect.
As an example if I try to update truenas, it just complains about DNS errors.
But if I connect to another DNS such as quad 9 it works just fine.
Is there something special I have to do to make truenas connect with its own VMs?
In the DNS field I have just put the IP The entire network uses to connect to the VM.
Running 25.04.1
Network is automatic bridged to my local IP range.
Well after following that tutorial the Host is no longer accessible. Which is strange because I hit test, which should revert changes after 60 seconds.
I dunno if something’s changed in the recent updates, but I have a (Windows 7) VM that was using a bridge adapter; it’s a file server which requires access to shares on the TrueNAS CE host. Out of interest a few weeks ago I changed it to use a physical NIC on the machine… and it works fine and has done since then.
When I originally set-up this VM on TN back in 2022, a bridge interface was mandatory but apparently no longer.
So after a config reset. I followed the same steps in the video. Once again adding the bridge completely breaks the interfaces enough where I don’t have web access.
The interfaces have been setup in a LACP config when before the bridge is configured.
Ok so I think there is some kind of bug with the version I am using. Doing these steps in the video just wipes the network config. So my LACP and bond just get deleted from the web UI.
I ended up making it on the local terminal and it appears to be working.
If the steps end up working for the VM I’ll follow up.
This was a massive pain in my ass. The first time broke it so much I had to reset to default. Hopefully the restore process will be simple.
After dealing with so much crap this didn’t work at all. I had to wipe defaults twice because each time either the network config would completely break to a point that even modifying it from the local terminal wouldn’t work. Then after all of that I just tried all the config on the local terminal, I got all the network settings to stay but the network for the VM just broke even more. I can ping the VM but I could no longer access the web interface along with any responses at port 53 which completely broke my DNS. So at this point I updated to the latest version of Truenas which made so many modifications to how VMs are handled I need to open a new thread. UGH!
