Stupid question from a new user.
first, i love pfsense its awesome to thanks everyone involved for making this!
My question, i want to setup dns forwarding but i want multiple entries for 1 ip address.
192.168.1.10:8081 -> service1.example.local
192.168.1.10:8082 -> service2.example.local
is this possible? if so how?
I tried and failed miserably to search for it. so if i missed a previous answer i apologize.
bryan.paradis last edited by
Can't do that with DNS records but you can do that with a reverse proxy. Try searching for squid + reverse proxy or multiple subdomains behind 1 public ip.
I am not sure exactly what your wanting to accomplish with your private IPs as clearly a non public fqdn with .local
Are the users all inside your network on 192.168.1.0/24 why do you want to use 8081 and 8082 internally?
What exactly do you want to happen here?
I have several internal web applications running on one server box. I'd like to make it so my users don't have to type in the IP address and port to connect to the applications. This is all internal none of these applications are accessible from outside my lan.
So when someone wants to use web application 1 they type in service1.example.local instead of 192.168.1.10:8081 (web applications are just using their default ports).
I mentioned DNS forwarder because that is where i found the host overrides option to map a hostname and domain to an ip address. If this is the wrong place then i'd love to know the right one :).
So lets say User A wants to connect to service1 on server in my LAN. currently they must enter 192.168.1.10:8081 or server.local:8081. I'd like for them to use service1.server.local instead. this will only be reachable internally.
I found that i can setup the 192.168.1.10 to server.local now but they still have to type in the ports. just want to get rid of that and be able to continue having all web apps on the same server.
I will definitely google squid + reverse proxy.
So these are internal - this really has nothing to do with pfsense, but more your webserver.
So pfsense resolves server1.local.lan to your 192.168.1.10 address. Great.. And you can also point server2.local.lan to the same IP.
Then on your webserver setup host headers if your running windows
or if apache its called virtual host named based.
So your web browser sends that it is looking for website called server1.local.lan so web server serves up the correct page. If looking for server2.local.lan it serves up different site, etc. All using port 80 http.
Or other option since your using rfc1918 space you should have plenty of IPs to work with - so just have your webserver with more than one IP, say .10, .11, .12 for how many sites you have. Then have server1 resolve to .10, server2 .11, etc. And setup your websites on this server to be served on those specific IPs.
edit: "I will definitely google squid + reverse proxy."
In your setup you have no need to use a reverse proxy internally. That is only when your limited to 1 public IP, and you need to send to multiple internal webservers based upon the fqdn/url your accessing.. Say you want pfsense to send server1.publicdomain.com that points to your 1 public ip on the pfsense wan to 192.168.1.10, but you want server2 still pointing your 1 public IP on the wan to be forwarded to 192.168.1.20 – this is when you would need a reverse proxy to look at the headers and say - oh you want server1 or oh you want server2
In your case where its all internal you have no need to use a reverse proxy.
bryan.paradis last edited by
If it is internal for sure no reverse proxy :)
sweet, thanks guys for all the help and pointing me in the right direction. ;D