Unable to browse machine via hostname

[Fiala06]

When I first setup unraid I was able to browse the machine via hostname. It now only works via IP. Not entirely sure when it quit.

 

Some things I've tried

• Reboots
• Added Dynamix Local Master
• Cleared my cache
• Multiple browsers and machines/devices
• Changing hostnames
• Unplugged ethernet cables to see if ip was being used by something else
• Switched from AMD Ryzen to Intel i9 (different motherboards/cpu/ram)

 

The network is All Ubiquity Unifi. Everything on the same network. 

 

Pinging hostname results in unreachable but dir IP works fine

 

 

Unraid etho

 

 

My primary desktop (physical machine)

 

 

Any ideas?

 

[Fiala06]

Interesting enough just found out if I ping unraid.local and put that in the browser it works. How can I remove the .local part as it used to work without it?

 

C:\Users\Fiala06>ping unraid.local -4

Pinging unraid [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64
Reply from 192.168.1.101: bytes=32 time<1ms TTL=64

 

[CarlosCo]

Hey! I not entirely sure if this has something to do with it, I'm a web developer and recall that not long ago google somehow start owning the .dev domain, that fact resulted in a local dev issue for a lot of web apps teams, some refs can be found really easy on the internet, (for example: https://developers.slashdot.org/story/17/11/30/1722233/wondering-why-your-internal-dev-web-app-has-stopped-working), so maybe Unraid guys implemented that feature or maybe the DNS software behind the scene got patched and now requires the specific .local, in my case is the same I need to use DOMAIN.local to get to the Unraid web UI

[Squid]

On 3/1/2019 at 10:24 PM, Fiala06 said:

unraid.local

Settings - Management Settings - Local TLD