Happy holidays everyone, pretty stuck on this one and would appreciate a second set of eyes to see if I missed anything obvious. I'm new to this, so apologies in advance if my understanding is way off.
Device: AC68U
Firmware: 386.12_4
My issue is that clients connected to the LAN directly have no problem resolving hosts via their DHCP <hostname>.home.arpa and their dnsmasq custom URL, but clients connected via the VPN can only resolve hosts via their <hostname>.home.arpa address.
As a concrete example: suppose I have a host called `rasppi` at 192.168.1.7. I give it a static IP in the DHCP server settings, and also add an entry to `/jffs/configs/dnsmasq.conf.add` pointing `rasppi.mycustomdomain.casa` to that static IP. Under this scenario:
and verified that VPN clients were able to resolve it.
Device: AC68U
Firmware: 386.12_4
Summary
I'm trying to set up remote access to my network via Asuswrt-merlin's built-in OpenVPN so that remote clients (my phone) can access hosts on my home network (eg a HomeAssistant instance running on a RaspberryPi). The router handles DNS and DHCP. All static hosts on the network have a URL under the router's domain (`<hostname>.home.arpa`). Some also have custom URLs under some other domain, configured through `dnsmasq` (eg `homeassistant.mycustomdomain.casa`). I describe below how this is configured.My issue is that clients connected to the LAN directly have no problem resolving hosts via their DHCP <hostname>.home.arpa and their dnsmasq custom URL, but clients connected via the VPN can only resolve hosts via their <hostname>.home.arpa address.
As a concrete example: suppose I have a host called `rasppi` at 192.168.1.7. I give it a static IP in the DHCP server settings, and also add an entry to `/jffs/configs/dnsmasq.conf.add` pointing `rasppi.mycustomdomain.casa` to that static IP. Under this scenario:
- On my home network, I can resolve `rasppi` at both `rasppi.home.arpa` and `rasppi.mycustomdomain.casa`.
- Outside the home network, connected to the VPN, I can only resolve it at `rasppi.home.arpa`.
Code:
address=/somebogushostbname.home.arpa/192.168.1.7 # this is the rasppi IP address
Current config
DHCP
- Enable the DHCP server on the router, and set the router's domain to `home.arpa`.
- Configure the "DNS and WNS Server Settings" per https://github.com/RMerl/asuswrt-me...mains-with-dnsmasq#adjust-dhcp-server-options
- I don't really understand step 3 in the link above, so I left "Advertise router's IP in addition to user-specified DNS" off, as the instruction seemed to suggest.
- Enable manual assignment and add a static IP and host name for each host under "Manually Assigned IP around the DHCP list".
DNS
- The DHCP "DNS and WNS Server Settings" described above should send the router's IP as the DNS server when clients connect to the network.
- Set up the router as described in https://github.com/RMerl/asuswrt-me...ains-with-dnsmasq#adjust-router-configuration
- DNS Director is OFF
- Add entries to `/jffs/configs/dnsmasq.conf.add` for the custom URLs:
Code:address=/rasppi.mycustomdomain.casa/192.168.1.7
- Under "WAN" -> "WAN DNS Setting", configure the upstream DNS server:
- DNS Server: 1.1.1.2
- Forward local domain queries to upstream DNS: No
- Enable DNS rebind protection: No
- Enable DNSSEC support: No
- Prevent client auto DoH: Auto
- DNS privacy protocol: None
Open VPN
General settings:- Client will use VPN to access: LAN only
- Interface Type: TUN
- Protocol: UDP
- Server Port: 1195
- Username/Password Authentication: Yes
- Username/Password Authentication Only: No
- Advertise DNS to clients: Yes