You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a wireguard network at 10.10.1.0/24 and ethernet at 10.88.111.0/24. Is there any way to custom the DNS response based on client IP? So that when I visit nas.lan from 10.10.1.2, the DNS response will be 10.10.1.100. When I visit nas.lan from 10.88.111.2, the DNS response will be 10.88.111.100. This will avoid machine in 10.88.111.0/24 forward the HTTP request via Wireguard relay server.
The text was updated successfully, but these errors were encountered:
I don't think blocky has the exact feature you are looking for. However, I can suggest the following.
Include both IPs in the response, with the LAN address first. Most clients will prefer that address and revert to using the second one if the first is not resolvable.
Use two instances, one for every network.
Configure the network routes on your network so that the same LAN IP is accessible from the VPN.
Ignore the issue. In my experience, the overhead added by the VPN tunnel is negligible.
I have a wireguard network at 10.10.1.0/24 and ethernet at 10.88.111.0/24. Is there any way to custom the DNS response based on client IP? So that when I visit
nas.lan
from 10.10.1.2, the DNS response will be 10.10.1.100. When I visitnas.lan
from 10.88.111.2, the DNS response will be 10.88.111.100. This will avoid machine in 10.88.111.0/24 forward the HTTP request via Wireguard relay server.The text was updated successfully, but these errors were encountered: