-
-
Notifications
You must be signed in to change notification settings - Fork 228
Description
Hi,
when not on VPN, domain points to public IP address, as expected. When using WireGuard (RethinkDNS Advanced mode) where I told it to use 10.0.0.1 (:53) as DNS server, RethinkDNS keeps using domain's public IP address instead of the one, i.e. 10.0.0.1 (:443), set in dnsmaq (used as lying resolver for that specific domain) on my server.
I do not have this problem on my laptops either thru macOS or Linux. It's just that on RethinkDNS/Android, my order is blatantly ignored. Doing a dig either on macOS or Linux outputs 10.0.0.1 for that specific domain under the ;; ANSWER SECTION: section, as expected when on WireGuard—I use the vanilla WireGuard app with 10.0.0.1 set for the DNS server.
In my case, I even forced rethink to exclusively use my own DNS: Configure ➝ Other DNS ➝ DNS 53 ➝ (then add 10.0.0.1:53) even though I already set 10.0.0.1 in the DNS section of the WireGuard client.
I tried to play with Firewall rules (IP & Port rules, per app), but not successful.
In my case, re-directing Nextcloud Talk domain to a local IP address inside the WireGuard network would enable me to fix that issue already discussed, but still not solved yet.
Context – Configuring WireGuard on the server was way easier for me than spending light years to configure TURN/STUN.