Multiple Hostnames for One Device in Local Network on Ugreen NAS

To assign multiple hostnames like nextcloud.local and nas.local to your Ugreen NAS 4800 Plus in a local network, set up a local DNS server such as dnsmasq on your Asus router or run Pi-hole in Docker—this overrides the router’s single-hostname DHCP limit and points all names to the same IP. For seamless access to services like Nextcloud without ports, pair it with Nginx Proxy Manager (NPM) on the NAS, routing traffic by hostname. You’ll get beautiful, memorable URLs across all devices, no more fumbling with IP:port combos.

Contents

• Understanding the Problem
• Solution 1: Local DNS Server for Multiple Hostnames
• Configuring dnsmasq on Asus Router
• Nginx Proxy Manager on Ugreen NAS
• Alternatives: Pi-hole and AdGuard Home
• Static DHCP Leases on Asus Router
• Testing and Troubleshooting
• Sources
• Conclusion

Understanding the Problem

Tired of typing your Ugreen NAS 4800 Plus IP followed by a port number every time you want to hit Nextcloud? In a typical local network, Asus routers let you assign just one hostname per device via DHCP—maybe nas.local—but not multiples like nextcloud.local or media.local for the same IP. That’s because standard DHCP hands out a single name based on the device’s MAC, and without a proper DNS server, everything falls back to messy IP addresses or editing /etc/hosts on every machine (a nightmare for phones and guests).

The fix? Introduce a local DNS server to map as many hostnames as you want to that one NAS IP. Routing services by name happens via a reverse proxy like Nginx. Why bother? It cleans up bookmarks, simplifies sharing, and feels professional. Your Asus router can even push this DNS to all clients automatically.

Solution 1: Local DNS Server for Multiple Hostnames

A local DNS server is your gateway to unlimited hostnames in the local network. Tools like dnsmasq let you define entries like nextcloud.local and nas.local both resolving to 192.168.1.100 (your NAS IP). Clients query this DNS instead of the router’s basic resolver.

This beats editing hosts files everywhere. As confirmed in networking forums, multiple hostnames per IP is standard—DNS just needs overrides or wildcards. For ports, add a reverse proxy later. Start by reserving a static IP for the NAS via DHCP to keep things consistent.

Here’s the beauty: once set, ping nextcloud.local from any device, and boom—NAS IP. No public domain needed; .local works fine internally.

Configuring dnsmasq on Asus Router

Many Asus routers (especially with Merlin firmware) run dnsmasq under the hood, making this dead simple. No extra hardware.

1. Enable SSH on your Asus router (Administration > System > Enable SSH, service restarts).
2. SSH in as admin, then su to root (default password unchanged?).
3. Edit or create /jffs/configs/dnsmasq.conf.add:

address=/nextcloud.local/192.168.1.100
address=/nas.local/192.168.1.100
address=/media.local/192.168.1.100

Save and exit. Reboot router or run service restart_dnsmasq.

In Asus LAN > DHCP Server, set “Use User-Defined Local Domain” to local (pushes .local to clients) and DNS server to router IP. Boom—network-wide resolution.

Users on SNBForums swear by this for exactly your setup. If stock firmware blocks it, flash Asuswrt-Merlin for full dnsmasq access.

What if no Merlin? Run dnsmasq in Docker on the Ugreen NAS itself—expose port 53, point DHCP to NAS IP.

Nginx Proxy Manager on Ugreen NAS

For portless access (nextcloud.local → Nextcloud on port 8080), NPM is gold. It’s Docker-friendly on Ugreen NAS 4800 Plus.

From MariusHosting’s guide, here’s the streamlined setup:

1. In Ugreen OS App Center, install Docker if missing.
2. Create a stack in Portainer (or direct compose):

version: '3'
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: unless-stopped
ports:
- '80:80'
- '443:443'
- '81:81' # Admin
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt

Deploy. Access admin at NAS-IP:81 (default: admin@example.com / changeme).

3. Add Proxy Host: Domain nextcloud.local → NAS internal IP:Nextcloud port (e.g., 8080). Enable “Block Common Exploits.” Forward Header: Host.

With your local DNS pointing names to NAS IP, NPM routes by hostname. Add more for jellyfin.local, etc. HTTPS? Self-signed or local CA for trust.

This combo—DNS + NPM—nails beautiful hostnames without router hacks.

Alternatives: Pi-hole and AdGuard Home

dnsmasq too fiddly? Pi-hole or AdGuard in Docker on NAS doubles as ad-blocker + DNS.

Pi-hole setup:

• Docker compose from official: expose 53/udp/tcp.
• Web UI > Local DNS > DNS Records: nextcloud.local → NAS IP (repeat for multiples).
• Set Asus DHCP DNS to NAS IP.

Unix Stack Exchange folks use this for local networks, pushing DNS via DHCP.

AdGuard Home: Similar UI, “Filters > DNS rewrites” for hostname/IP pairs. Lighter on resources for Ugreen.

Both beat router limits. Bonus: blocks ads network-wide. Drawback? NAS downtime kills DNS (mitigate with router fallback).

Static DHCP Leases on Asus Router

First step for any solution: lock NAS IP.

Per Asus FAQ, LAN > DHCP Server > Enable Manual Assignment. Add NAS MAC → fixed IP (e.g., 192.168.1.100).

Also this FAQ covers IP binding. Now DNS entries stick—no IP drift.

Pro tip: Set hostname there too (nas.local), but override with DNS for multiples.

Testing and Troubleshooting

Test: From phone/laptop, nslookup nextcloud.local (should show NAS IP, your DNS server). Ping it. Browser: nextcloud.local loads via NPM.

Issues?

• Name not resolving? Flush DNS (ipconfig /flushdns Windows, systemd-resolve --flush-caches Linux). Check Asus DHCP pushes correct DNS.
• Port conflicts? NPM on 80/443? Free 'em first.
• Ugreen firewall? Allow Docker ports.
• From ServerFault, confirm no TTL weirdness—defaults fine.

Router logs (System Log) show dnsmasq queries. All good? Share nextcloud.local with family.

Sources

1. Multiple hostnames for a single IP address in local network — Stack Exchange guide to dnsmasq address overrides in local setups: https://unix.stackexchange.com/questions/724654/multiple-hostnames-for-a-single-ip-address-in-local-network
2. How to use your own domain name on your UGREEN NAS — Step-by-step NPM Docker install for Ugreen NAS with proxy hosts: https://mariushosting.com/how-to-use-your-own-domain-name-on-your-ugreen-nas/
3. Add local DNS entries on my ASUS RT-AC68U — SNBForums thread on dnsmasq.conf.add for Asus routers: https://www.snbforums.com/threads/add-local-dns-entries-on-my-asus-rt-ac68u.29504/
4. How can I use DD-WRT to resolve multiple hostnames to one IP address — SuperUser on dnsmasq syntax for multi-hostname mapping: https://superuser.com/questions/1177192/how-can-i-use-dd-wrt-to-resolve-multiple-hostnames-to-one-ip-address
5. ASUS Router DHCP Server Manual IP Assignment — Official Asus FAQ for static leases by MAC: https://www.asus.com/support/faq/1011703/
6. ASUS Router IP Binding — Asus support on DHCP reservations for consistent local IPs: https://www.asus.com/support/faq/1000906/
7. Is it possible for two hostnames share the same IP address — ServerFault confirmation of multi-hostname feasibility: https://serverfault.com/questions/517501/is-it-possible-for-two-hostnames-share-the-same-ip-address

Conclusion

For your Ugreen NAS 4800 Plus in a local network, dnsmasq on Asus or Pi-hole delivers multiple hostnames effortlessly, while Nginx Proxy Manager handles service routing like Nextcloud without ports. Start with static DHCP, add DNS overrides, test thoroughly—you’ll wonder how you lived with IP:ports. This setup scales to more services, stays private, and works across devices. Dive in; your network deserves beautiful names.