Pfsense does not resolve domain on my lan
-
I have a home gitlab server in which I have applied the corresponding rules in NAT / Port Forward to be able to access from outside my Lam network.
The problem arises when I try to enter from any computer on my Lam, when putting my domain this is not resolved I can only enter using the server's ip.
What should I do to be able to access my server using my domain, instead of the IP of the gitlab server. -
Have you created host overrides in the DNS resolver page?
-
@jknott said in Pfsense does not resolve domain on my lan:
Have you created host overrides in the DNS resolver page?
Yes
-
@themac Post a screenshot of what you did and some example output of what you see when you try to resolve.
-
@kom said in Pfsense does not resolve domain on my lan:
@themac Post a screenshot of what you did and some example output of what you see when you try to resolve.
resoled
-
@themac And your solution was.....?
-
@kom said in Pfsense does not resolve domain on my lan:
And your solution was.....?
Install bind as a local DNS server so my domain was not resolved locally -
I never needed bind to that.
The default pfSense settings - two lines to edit, did that for me :
And bang, now the entire network knows it's part of the domain name (see image).
And pfSense knows it's called pfSense.Let's check :
More checks :
I used a magic trick :
Didn't had to change anything on the Resolver setting page neither.
Use the default and you're good.
I tend to say : " don't break things if toy want it to work. "Because I own (== I rent) this domain name, and because I do my own domain name server handling on a dedicated server some where on the Internet I can now do click-click install acme and hoppa, real trusted certs for me.
Free Dynds for all my devices with some more clicks.
( DNSSEC while you're at it - but this time the mouse will abandon you, a head, some brains and a keyboard are needed)
The name server uses bind ,of course.But why role out the tank if you can wipe the bug with a bug wiper ?
