I assigned static IPs to my devices, and managing my network got much easier

Published Aug 13, 2026, 1:46 PM EDT Ismar is a Senior Author at How-To Geek. He previously worked as a writer, editor, and general manager at a content agency before joining the team in 2023. He began his writing career in 2021 after completing a BA in English Language and Literature. Beyond How-To Geek, Ismar has contributed to Red Stag Fulfillment and Authority Hacker. He has also worked on various SEO projects to help clients improve their search visibility. Ismar has been around Windows PCs since the age of three, so friends and family naturally chose him as the resident tech support. His projects often involve tinkering, such as disassembling mechanical keyboards and gaming mice to mod his beloved gear. He also enjoys pushing hardware to the max through overclocking while staying on a reasonable budget. An avid gamer, Ismar has logged thousands of hours across various genres, including first-person shooters, RPGs, racing games, and roguelites. When he is not at his desk, he is probably exploring other people’s phones to discover their quirks and features or experimenting with the latest AI tools. In his free time, Ismar enjoys spending time with his wife, working out at the gym, playing guitar and bass, cooking gourmet meals, and traveling. Above all else, he’s a proud cat owner. By default, a router's DHCP server assigns IP addresses to devices as they connect to the network. Frankly speaking, this works fine for most households, but when you're into self-hosting and want more control over a network filled with devices, constantly changing IPs are a massive headache. After assigning static IPs to all of my mainstay devices, my life became a lot easier. Here's why. My home server and self-hosted services stay put No more IP hunting if the server goes down I turned my old laptop into a DIY NAS earlier this year. It later grew to become my media server and general-purpose homelab server. After setting it up as a headless server, one of the first problems I noticed was that its IP address kept changing whenever I rebooted it. So, I assigned the NAS a static IP, and I could finally stop hunting down its newly assigned address in the router's control panel whenever something went wrong. But easy access was really just the beginning. With a static IP, I could consistently access Home Assistant, Jellyfin, Sonarr, Portainer, Immich, and all my other self-hosted apps because the server was always available at the same address. This is also useful for apps that need to communicate with each other or that I've configured to connect using the server's IP, since I don't have to worry about those connections breaking after a reboot. I also still use my home server as a regular NAS, so having a predictable IP makes it much easier to connect to shared folders from my desktop, laptop, and other devices. I don't have to figure out where the NAS moved every time its IP changes. And should I ever decide to expose one of my services to the internet, having a predictable local IP will also make things like port forwarding and DNS records easier to manage, since I know exactly which machine incoming traffic needs to reach. Troubleshooting and making sense of network traffic got a whole lot easier No more mystery IPs For a while, my home server was actually the only device on my network with a static IP, but as I kept running into various problems, this eventually grew to encompass every device on the network. To be more specific, I started self-hosting AdGuard Home. This acts as a DNS server for my entire network, and thanks to some strict DNS blocklists, I was able to reduce the load on my humble network connection while also blocking unwanted telemetry and tracking. Unfortunately, AdGuard Home was working a little too well, and it started blocking important websites. More specifically, it blocked some random websites that my wife uses for work. Since she was constantly complaining about not being able to research some pretty niche topics for her job, I decided to assign static IPs to her laptop and phone and allow them to bypass the filters for unrestricted browsing while still retaining the benefits of a self-hosted DNS server. I also added my own devices to the list, which gave me an easy way to keep track of what's being filtered in real time. If I notice a website or app isn't working correctly on my desktop, I can simply enter the PC's local IP address in AdGuard Home and check the timestamps of recently blocked queries in the log. Recently, I noticed the Xbox app wasn't working correctly on my desktop, and I was able to fix it by unblocking some Microsoft telemetry just on my desktop while keeping it blocked everywhere else. Without a static IP, I'd first have to figure out which address the PC currently has, adding an unnecessary step every time something goes wrong. More importantly, I wouldn't be able to keep that exception tied specifically to my desktop if its IP changed with each boot. My smart devices finally stay local and predictable No more disappearing devices Credit: Ismar Hrnjicevic / How-To Geek With all of my primary devices assigned a static IP address, the only devices left were my IoT gadgets. Most of them are just simple smart bulbs, plugs, and sensors, but since I've got so many of them, they actually make up the bulk of my network. For a while, I didn't really see any benefit to assigning static IP addresses to them, especially since it would've taken me a while to do so. However, this all changed when I decided to move away from cloud-based controls. I was getting tired of these cheap lights randomly becoming unresponsive and disconnecting, leaving me with no way to turn them off. That's when I discovered Tuya Local, a Home Assistant integration that lets you control compatible Tuya devices locally, without relying on the cloud. An essential part of my setup was assigning a static IP to each device, so I headed over to my router's control panel, wrote down the MAC and IP address of each device, and created a static IP reservation for them. After I finished setting everything up, I decided to take these devices offline completely by restricting their internet access. I initially did this through the parental controls on my router, but AdGuard Home suspiciously showed that the devices were still "calling home" and remained accessible even with the Wi-Fi on my phone turned off. So, I headed over to AdGuard Home, took the list of IPs for my IoT devices from the router, and permanently blocked internet access for those devices, along with a network-wide block on the cloud service used by these Tuya gadgets. Just like that, all of my IoT gadgets became permanently offline, which made them much easier to monitor and manage while still letting me control them locally. Static IPs work even better with a naming system Static IPs are incredibly useful if you have a lot of devices on your network and want to manage them more easily or simply keep track of what they're doing. That said, I made one massive mistake when assigning mine: I used whatever IPs the router happened to give those devices at the time instead of creating a proper structure with dedicated ranges. Fixing that now would mean going through every device and reassigning its address. If you decide to assign static IPs, I'd recommend creating a proper structure from the start. For example, you could use .10–.49 for computers and phones, .50–.99 for IoT devices, and .100+ for guest devices. That way, you can often tell what kind of device you're looking at just by glancing at its IP address.