Pfsense not resolving via Traefik proxy, which previously worked.
-
Hi all,
New to this....The issue I have come up against is the following.
Currently moved form a Virtual pfsense instance to a hardware dedicated instance.
I run Traefik proxy behind the FW to give my SSL to all my services that I run behind the FW.
After migrating to the new pfsense the only thing that does not work via traefik is pfsense WebGui, everything else no issue.DNS flow as follows for none public domains :
PC Request -> Pihole (Adblock only) -> pfsense (DNS Resolver domain override) -> Local Bind9 Server -> Traefik -> Service
Some initial testing/fault finding :-
NSLOOKUP for pfSense using its working configured local domain in Traefik :
user@linuxpc:~# nslookup pfsense.home.local Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: pfsense.home.local Address: <return pfsense internal IP not the expected IP>
NSLOOKUP for Authentik. using its configured local domain in Traefik
user@linuxpc:~$ nslookup authentik.home.local Server: 127.0.0.53 Address: 127.0.0.53#53 Non-authoritative answer: Name: authentik.home.local Address: 192.168.xxx.xxx <returns correct Bind9 configured IP for traefik>
NSLOOKUP for pfsense.something.local using directly using the Bind9 server IP
user@linuxpc:~$ nslookup pfsense.something.local 192.168.1.4 <bind9 ip> Server: 192.168.1.4 Address: 192.168.1.4#53 Name: pfsense.home.local Address: 192.168.xxx.xxx <returns correct Bind9 configured IP for traefik>
Using the Authentik domain name in the browser opens the authentik webpage with a secure SSL
Using the pfsense domain name in the browser does nothing but times out.Any help or pointers would be great.
-
@linuxtechstuff Found the solution :-)
-
@linuxtechstuff Please could you tell me how you resolved this?
regards
cyber7