MandolinJeff

And the address range for a static IP has to be reserved for static IP's. So if I let it assign an address from the DHCP pool and then try to make it static, I'll have to carve that address out from the DHCP pool. So instead I changed it to a range (3) I already had set up for static IPs. Either way it looks like I may be going back to 43 regardless. I now suspect it has to do with TLD and DNS Rebinding being blocked by OPNSense.

I'm using OPNSense as a router. So I'm using a small range of IP's that I set aside for use as fixed IP's. AFAIK it doesn't really do reserved leases. At least not the way most consumer routers do.

Started out with UNRAID this morning and began transferring my Plex and Channels DVR server to it, as well as a bunch of files that I want to archive. Initially I was accessing it the web GUI via http://tower, and my server had received the IP address of 10.0.0.43 via DHCP, I switched the IP address to a fixed address of 10.0.0.3. Afterwards I can now only access the web UI via the IP address, and not by using http://tower address or tower name. The server also still shows up as "TOWER" when I explore the network using a windows machine, but it will not display any shares. I think I obviously broke something when I switched the IP to a different fixed address. It's not at all critical, but I'm hoping the fix to get the server accessible by its name again will be pretty easy. Can anyone point me in the right direction? Thanks!