I'm having trouble getting unraid to respect the Local TLD setting I put on the management access page.

 

I purchased a new domain (ie. domain.dev) on google domains.

I setup the Local TLD to 'domain.dev' and then applied it and saw the screen updates to say I can use 'http://tower.domain.dev' to access it.

I try it and it doesn't work, ip access still works, and the previous hostname 'http://tower.local' still works, so I rebooted and same result.

I doublechecked the ident.config is getting updated on the flash drive, so I know the setting it sticking. I didn't turn on ssl yet.

 

Do I need to setup DNS on cloudflare or my router to resolve this? I was thinking it would work auto-magically like the 'http://tower.local' one did.

My end goal is to access my local resources internally by that new domain with nginx, but I'm stuck at the getting the new local hostname to work.

 

(I'm running 6.11.5)

 

Edited July 14, 20232 yr by arkhan4
added the unraid version

The .local domain uses Multicast DNS ( https://en.wikipedia.org/wiki/Multicast_DNS ) so an actual DNS server is not required. It is the only domain that works that way though, all other domains require a DNS server.

 

The easiest solution would probably be to use the DNS server that your domain registrar provides, assuming they let you point at internal IPs. Cloudflare can work too. Note that you may need to disable DNS Rebinding Protection on your router and/or DNS servers to let clients resolve local IPs for FQDNs.

 

You may find this page of the docs helpful:
https://docs.unraid.net/unraid-os/manual/security#securing-webgui-connections-ssl