Hello, very new to all this. I installed PiHole and tried updating my DNS on my router to the IP of my NAS. My desktop became very laggy so I killed the web GUI and reset the DNS settings on my router. I wasn’t able to reopen Truenas in a new instance so I powered down the NAS and restarted it. Still wasn’t able to connect until I plugged in a monitor and realized that the IP had changed. I had already setup 2 network drives on 2 PCs so I wanted to change the IP back to what it was. I went to the network tab, went to edit the interface, unchecked DHCP and Autoconfigure IPv6. Clicked add and put in the old IP. The CIDR on the IP after the reset is 22. I’ve tried both 24 and 22. I click save. I’ve tried skipping the default gateway and putting in the old IP address. I click test. It thinks for a little then I’m presented with a screen saying “Connecting to Truenas”. I attempt to login to the gui with the old IP address and it never resolves. I did notice that the last digit of the default route is .0 which matches the IP after reset. The IP before reset had .68.
I’m not too deep yet so rolling with a new IP is not that big of a deal. I’m not sure how to delete the network drives as they show disconnected on my 2 PCs and nothing I do will delete them. Any help would be appreciated
Why should your desktop become laggy because of a DNS setting?
Do you run Windows that access a network share on TrueNAS and your explorer got laggy?
Also has nothing to do with setting the DNS on your router.
This leads me to believe that you setup something wrong on your router or pihole.
Maybe you have enabled DHCP on pihole and now two DHCP servers in your network? That would explain the TrueNAS behavior.
22 is equivalent to 255.255.252.0. Unless you are a network pro and know what your are doing and need more than 254 devices, you probably have 24 which is quivalent to 255.255.255.0
Well a network share and with Pihole, it directs the traffic from the router through the TrueNas Pihole adblock and then it comes to my desktop. The NAS is a brand new 14100 with 32GB of ram. I didn’t notice any lag in the windows explorer the NAS is currently completely empty. I was trying to initiate any services I might want to run before filling it up.
I’ll try to investigate this further. I followed this (www. youtube. com/watch?v=Td4E2cCNh_Q&ab_channel=LoResDIY) guide to setup
The original IP was 192.168.68.67. After reset it is now 192.168.0.66. Any attempts to change it back to 192.168.68.67 have failed.
You need to find the dhcp settings on your router and set them correctly. Perhaps look at its manual. There should be some setting to always assign the same up to the NAS. If not, look for a setting or statement of he dhcp range, then set the ip of your nas manually to some ip outside the dhcp range but inside your subnet.
I don’t try to be a dick, but what you are facing is exactly the problem with these YT influencers. They try to sell you something as easy and copy paste, while in reality you have to at least understand some underling basics. Otherwise you will run into one wall after another.
Starting your journey with TrueNAS (ZFS) and pihole on top in a VM is like starting jogging by doing a half marathon. I don’t say running half marathon without training isn’t possible, it is just a pita.
If you still want to go down that route, do the following to make it as easy as possible
start with your routers defaults
set the DHCP to hand out IPs from 192.168.1.50 to 192.168.1.250
in the DHCP settings, set the handed out DNS to 192.168.1.2
set TrueNAS to use DHCP
create a IP reservation for truenas on your Router
run pihole on 192.168.1.2 (either by setting a static IP or by reserving it on your router)
if your router does not support these settings you can alternatively do
start with your routers defaults
disable the DHCP server on your router
set TrueNAS to use DHCP
start pihole and configure it to have the static ip 192.168.1.2
@Drew_Van_Harden, welcome to the forum. Besides doing what @ThisMightBeAFish said to do, I would set your CIDR to /24. It has been my experience when dealing with a Class C IP version 4 address (192.168.x.x) on modern routers; anything above /24 I have issues with it.
I don’t know why my first IP was what it was but the new IP has persisted through a couple restarts. I set my IP to be static and set the default to be my router’s IP address. I will use the /24 going forward.
One thing to point out is that Pihole does not route traffic. Traffic does not flow through Pihole. It acts as a phone book. Want to make sure you understand what each piece of the networking setup actually accomplishes. Sometimes that’s half the battle in finding the true problem to the issue.
