normtown

Sorry for the delay. This is happening with any browser. The browser doesn't matter though. I can't even ping tower.local from the command line.

The way it works with a DIR-825 is that you can reserve IP addresses in the DHCP server's IP range for specific MAC addresses. This guarantees that when the DHCP server sees that MAC address it will give it that IP address. This does not guarantee that the router knows how to route traffic to that host. If you're not using a DNS server the host needs to broadcast its name for that to happen. I appreciate the workarounds being suggested. I'll look into OpenWRT. I still think we should find the root cause however.

@unevent Thanks for the info. I can't make heads or tails of what that link is saying. Care to translate for me? @drawz I'm using a D-Link DIR-825, hardware version B, with firmware 2.07NA.

Secondly, I don't expect to get anything meaningful from nslookup because I don't have a DNS server. Using nslookup both before and after tower.local in un-pingable gives: $ nslookup tower.local Server: 208.67.222.222 Address: 208.67.222.222#53 ** server can't find tower.local: NXDOMAIN $ nslookup tower Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: tower Address: 67.215.65.132 In the second case, I clearly left the LAN because it's just some opendns host: $ dig +short -x 67.215.65.132 hit-nxdomain.opendns.com.

Firstly, on the unRAID server, I ran ethtool and ifconfig: ~# ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes ~# ifconfig eth0 Link encap:Ethernet HWaddr bc:5f:f4:83:ef:71 inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2467498 errors:0 dropped:198 overruns:0 frame:0 TX packets:923886 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3280671312 (3.0 GiB) TX bytes:64237367 (61.2 MiB) Interrupt:46 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:917 errors:0 dropped:0 overruns:0 frame:0 TX packets:917 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:76862 (75.0 KiB) TX bytes:76862 (75.0 KiB)

Attached! syslog.txt

I just verified that I get the same behavior when using a static IP address. Tower appears at first and is pingable as tower.local, then it disappears after a little while and is no longer pingable by the hostname.

I can't ping tower from any host in my network either. @EGOvorhuk I'm a little confused by your test. My networking knowledge is admittedly limited. If you set a static IP in the web GUI but don't reserve that IP in your DHCP server, should your router know about it? It's not clear to me that the behavior you're seeing is unexpected. Can anyone educate me on this? Also, when I reboot (using DHCP for IP assignment) I see Tower in my device list and it is pingable via tower.local at first. After a little while (not sure how long exactly--5 to 30 minutes, maybe?) tower.local becomes unpingable.

I understand your frustration regarding the advertised services from avahi. However, that is not really what this thread is about. If you have any solutions or clues about the root cause of the original issue I reported, please feel free to contribute. It sounds like the integration with avahi coincides with this hostname behavior. Are there any unRAID devs that can speak about the integration?

I do use AFP. Creating the Tower and Tower-SMB crap is exactly what I want it to do This is affecting more than just the creation of Tower and Tower-SMB. As I said before, it seems as though the unRAID server is not broadcasting its NetBIOS hostname to the LAN. I can't even ping the server with its hostname. The only thing that seems to make it broadcast again is restarting my router. I'm guessing that the process of getting a new IP address from my router's DHCP server causes the unRAID server to broadcast its hostname. I'm guessing there's a TTL on that?

My guess is that there's something funny going on with the NetBIOS integration. I'm guessing that because I'm just running a simple LAN with a few machines connected to a router. For my unRAID server to disappear after a little while it would have to stop broadcasting its name to the other hosts on the LAN. Was this happening in 4.x? Have there been any changes in this area?

I'm noticing that I can connect to my server by its hostname ("tower.local") when the server is started, but after "a while" (usually no longer than 30 minutes) the hostname is no longer resolvable. I can still connect by IP. Has anyone else seen this behaviour? I'd like to continue to used DHCP for IP assignment and not resort to hacking my hosts file. This should be something that works without resorting to those kind shenanigans This is my first unRAID build. I'm running 5.0 rc-16.