Accessing via server name not working (ip address fine)

Hello,

Have updgraded to OMV7 and the only minor (but irritating) snag I'm experiencing is that I used to be able to access the NAS via servername but I now i'm forced to use the ip address (either to access via Mac's connect to server or to access the wbe GUI). The only is exception is my Windows machine where the servername is recognised. My other devices a Mac (Sonoma 14.7) and Google Pixel 7 phone can only access via ip address. It was definitely the case that I could access by the servername on all devices, though I do remember I had a similar issue when I first configured OMV (my first version was OMV 6). I can't remember if I resolved it by altering a setting or if it just fixed itself! Appreciate this is no biggy but I am curious as to what the issue is. See config in signature.

• Have tried adding '.local'. Doesn't make a difference.
• The server is assigned to a static ip on my router

Thanks in anticipation of any support. Cheers!

Thanks both for the suggestions. I'll look into the hosts file config as I appreciate this'll just force a fix but it's odd that I haven't had to do this previously.

Quote from donh

On the omv cli nslookup 'omv ip" "dns ip" will show what the dns thinks is the name of your OMV.

Tried this command (by omv cli, assume you mean through ssh)? The command just hangs. with "< " as the result. Perhaps this is the issue?

Quote from Zafkiel

I previously encountered a similar situation where my Windows machine couldn't access OMV via hostname, but my phone could. Later, I found out that my computer had a VPN running, so you might want to check if you have such software running.

Or run hostname -f in the OMV command line to check what the hostname is, and then make sure you're opening it with http, as OMV defaults to http and not https.

Thanks - No VPN for me me. The 'hostname -f' command shows as expected.

Quote from donh

nslookup 10.0.1.1 10.0.1.2  Replace 10.0.1.2 with omv ip and 10.0.1.1 with the dns server ip (router) I guess. There should be a way to add the name and address to the router. That is called revers dns lookup.

Thank you. Result is:

** server can't find 156.1.168.192.in-addr.arpa: NXDOMAIN

Thanks all for replies.

Quote from donh

Google your router and dns settings. There should be a way to add an entry for your OMV. If not Google your OS and "hosts file" and add an entry there.

Yeah I can't see a way in my router to sort in the dns settings (it's a crappy propriety router from my broadband provider). Hosts file on devices is probably the only way.

Quote from BernH

you can also add the a .local to the server name

Thanks but as mentioned i'm including this.

Quote from crashtest

The way I set up a crude sort of local DNS is at my DHCP server (which is typically the gateway router).

When I set a static IP address at a server, I also a setup static DHCP lease for the same IP address for the same server. That maps a server's hostname to it's IP address. When name lookup's are sent to the gateway, the gateway returns the address from the static DHCP lease.

Not really seeing any DHCP config settings on my router unfortunately.

Quote from crashtest

If you don't have a dedicated DHCP server on your network, your gateway router is (most likely) handling DHCP requests. Consider consulting the router's OEM's doc's or look it up on the OEM website.

To configure a static DHCP lease, you'd have to manually enter the lease at your router. When you find where to do this, on your router, there are 3 entries in a static DHCP lease.

1. The mac address. (This can be found on OMV's CLI by using ip add. Your interface name may be different from eno1.)



2. IP address (The same IP address used to statically address the server.)

3. The Host Name. (This should match the host name entered under Network, General, in the Hostname field.)

While the web page presentation will be different, on your router, it might look something like this:
(Click to expand)

Display More

Thanks, appreciate the assistance. Have explored my router's settings thoroughly and the only page that resembles your screenshot is the assigning to static ip address which includes reference to the server name. But this was already done (I've tried removing the assignment and re-adding with multiple router & device restarts but it hasn't fixed it). I do feel this must be something OMV as the only change is the upgrade. The router and devices have remained the same. Oh well! Perhaps it's an issue with my router in the end. For now I've edited the hosts file on my Mac and I guess i'll have to do the same for my other devices or just memorise the ip address! Thanks all for the help anyway.

Quote from donh

Can't check now but 6 may have used mdns as well. 7 may not. There aren't many name resolution protocols.

Your router may require a power cycle for changes to apply.

Thanks. Not really familiar with mdn. Have rebooted router/all devices multiple times.

Update to this - having started exploring Dockers, curiously my dockers work with the server name. It's just the main OMV web gui that isn't resolving the hostname. In case that helps diagnose this issue!

Thanks for the reply but there's no option to do this in my router.

Quote from crashtest

Does not equate to the following.

Believe me, I have looked through every page on my router's config and there is absoluitely no option to resolve hostnames to an ip on this router. It's a vodafone router and I have searched their forums and it seems other people agree there isn't the option to do this

Quote

- Set a static DHCP lease

Do you mean set the raspberrypi to have a static ip? I've done this. The ip isn't the problem, it's resolving the host name.

Quote

As mentioned, no option to do this

As I say, I'd be inclined to suspect it is the crappy router at fault, but it is definitely something that's been caused by an upgrade to OMV7. The fact I'm able to resolve the hostname through the dockers supports this.

Screenshot of LAN page (some personal data redacted). Happy to provide screenshots of other pages to prove what I've said and gladly eat incorrect pie if there is a way: