Hi guys, maybe a dumb question but I’m pretty clueless when it comes to networking.
Background:
I have a mini PC set up with some self hosted apps and traefik. I used duckdns as a DDNS. For example I have app1.mydomain.duckdns.org. Everything was working fine when I was using my router from xfinity.
Now I got the Flint 2 and put my xfinity router in bridge mode and connected them.
I set up a wireguard server on the flint 2. The settings recommended using a dynamic DNS with the VPN so I enabled that as well. VPN server is working fine.
I also port forwarded 80 and 443 so which traefik requires. However, now whenever I go to app1.mydomain.duckdns.org, it resolves to the admin/config page for the GL iNet router.
Does anyone know what could be causing this and how to fix it? I’m guessing it could be because of the DDNS set on the router but really I have no idea.
I’m not home right now to troubleshoot but I will be later so I could provide configs or logs for anything. When I check app1.mydomain.duckdns.org on a DNS checker it gives my public IP.
Just disconnected from my home VPN (currently on phone) and what do you know, it works.
I’ll have to look into this more when I get home, but does this mean I won’t be able to access any of my apps from app.domain.duckdns.org when I’m at home on my local network? That’s not ideal. Do you know a way around this?
I’m about ready to take all my services off the reverse proxy and just access them through VPN when I’m away, however the reverse proxy is an easy way to provide https certs which some of my services (Actual Budget) require.
The issue: For this setup, you need to have a split-DNS-situation.
Inside your home network, the domain app1.mydomain.duckdns.org needs to resolve to the local IP of the server that provides your web applications.
From outside, it must point to the public IP of your router - like now.
Hey thanks again! I guess this is something I could solve using the DNS rewrite filter in Adguard home? I’m not entirely sure how to do this but I’ll do some research. So my goal would be for adguard to route *.my domain.duckdns.org to the IP for my reverse proxy (traefik)?
When you say local IP, would that be the IP of the docker container for traefik? Or the IP of the PC running docker? I guess I can test it both ways.
In adguard, i set it to rewrite *.mydomain.duckdns.org to 192.168.8.215 (local IP of PC running traefik)
At first just that didn’t work, the key was to set the DNS in my wireguard config to use 192.168.8.1, for some reason the generated config was using a different DNS.
