So I recently got pisession kf a nas with OMV on it. That has a webinterface that I can reach from my laptoo via "openmediavault.local". But I never defined anywhere that that adress leads to the IP of my server. Better still, if I restart my server an DHCP gives it a new IP, "openemdiavault.local" still works.

How does that work? And can I make an andress like "radar.local" that automatically points to my radarr webinterface no matter hwat it's IP is?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 weeks ago

It's just regular LAN DNS behind a masquerading router. Inside your network services can get names in a few ways

  1. A hosts file mapping IP address to a name placed on any machine that wants to use names. Downsides: not automatic, hard to update in a dynamic DNS environment. Works fine if you assign every service a static address (my printer always gets 192.168.1.5, for example — configured in the router(

  2. Have the service respond to a DNS offer with "thanks, my name is fileserver" and the router can resolve fileserver.local to 192.168.0.203

I use host files and my addresses below 192.168.1.100 are reserved for static addresses and my half dozen things I want to address by name get one of those addresses

  • source
  • parent