Hey over there,
i have following issue, where i want to create a smooth and easy network flow and i am a bit stuck.
I have an Asus ax86u (MerlinWRT 386.3_2) running on 192.168.1.1. Netbios name for example https://router.homelan => works.
I have an Synology DS220+ (DSM7) running on 192.168.1.123. Netbios name for example https://device.homelan => works.
I want to acess for example Synology Calender.
The build in Adress is something cryptic like "https://synology.homelan/caldav.php/{username}.
Goal is to reach it via "https://caldav.synology.homelan".
I had already played around with reverse proxy & nginx reverse proxy in a docker, trying to reroute (especially because the ports-problem).
Nslookup tells me, that the request for "caldav.synology.homelan" is not even getting routed to "synology.homelan", because the router interprets it as a new host.
So in my perspective, i have 2 options:
1) adding (all subdomains /wildcard subdomains) in the router (hosts, dnsmasq.conf, [anywhere else])
2) running an own LAN DNS Server (for example on 192.168.1.123 [synology.homelan]), and use it here:
So. can someone agree? or are there better (already built in) options, i dont see?
And yes, this is just in LAN. I dont want to expose my Synology to the WAN (yet). Access over OpenVPN (on ax86u.home) with ddns is granted.
Thanks in advance
i have following issue, where i want to create a smooth and easy network flow and i am a bit stuck.
I have an Asus ax86u (MerlinWRT 386.3_2) running on 192.168.1.1. Netbios name for example https://router.homelan => works.
I have an Synology DS220+ (DSM7) running on 192.168.1.123. Netbios name for example https://device.homelan => works.
I want to acess for example Synology Calender.
The build in Adress is something cryptic like "https://synology.homelan/caldav.php/{username}.
Goal is to reach it via "https://caldav.synology.homelan".
I had already played around with reverse proxy & nginx reverse proxy in a docker, trying to reroute (especially because the ports-problem).
Nslookup tells me, that the request for "caldav.synology.homelan" is not even getting routed to "synology.homelan", because the router interprets it as a new host.
So in my perspective, i have 2 options:
1) adding (all subdomains /wildcard subdomains) in the router (hosts, dnsmasq.conf, [anywhere else])
2) running an own LAN DNS Server (for example on 192.168.1.123 [synology.homelan]), and use it here:
So. can someone agree? or are there better (already built in) options, i dont see?
And yes, this is just in LAN. I dont want to expose my Synology to the WAN (yet). Access over OpenVPN (on ax86u.home) with ddns is granted.
Thanks in advance
Last edited: