Sounds like to me you don't really know what you want. I can only answer you questions as asked - can't read your mind.  You could have 100 servers, you could hae 1 server serving up 100 different fully qualified domain names via host headers, you could have 1 server with 100 IP address. Comes down to the same thing you only have 1 public IP.  If you want to use the same name site.domain.com to get there you can only distinguish via ports like shown.  Or if you want to use a reverse proxy to see sitea.domain.com and send to 192.168.1.100, and siteb.domain.com to 192.168.1.101 be it 1 server or 2.. What you can not do is have pfsense out of box know that you want to send sitea.domain.com to 100 and siteb.domain.com to .101 since it only sees the public IP your hitting and a PORT..

You are 100% correct.  The WAN interface did not have a default gateway selected in the WAN interface page.  The default GW was there though in the routes table, so I just selected it in the WAN interface page and now automatic outbound NAT properly creates the auto rules.  Thank you for your help.

I have also seen some pages use some JavaScript and/or WebRTC trickery to find the local IP address, but usually a proxy and X-Forwarded-For is the culprit.

Ah, thank you!  sorry to CMB, I sware I saw the "thing" grey out and can not move.  but I moved it now, I'll go test, probably should work now. Thanks again for the help!

:D Problem solved problem solved, it was actually the default gateway, I pointed to my server 2 pfSense router and everything works

Thats awesome.  Should help the new guys alot.

oh yeah i know its easy to turn off and on, but i have a widget on my home screen, so that means i would have to have it on all the time otherwise the widgets wouldnt work, but its not a major problem. And with my work, no need to bounce via proxy ..

So simple. Thank you for your help.

Hey Ryan Im in the same boat you are. did you ever get a full response or find an answer that worked. any help would be awesome thanks Eric

Services - DNS Forwarder - Host Overrides

I had this same issue just recently. I can ping the DMZ interface IP from LAN, but cannot ping hosts behind DMZ interface. This was fixed by fixing the mistake I made during IP assignment in DMZ interface. In DMZ static IP configuration i assigned a subnet of /32 which should be /24. After the fix i can now ping hosts behind DMZ interface.

KOM and Derelict, I added the alias and the firewall rules, and it's working beautifully. Piece of cake. I just needed a nudge in the right direction.  8) Thanky you! Eric

Ok, sorry about that! Thanks for help me Regards

Yeah - over a long haul, having that UDP port open SHOULD knock off alot of laggyness. I use UDP VPN myself.  I'm not a big fan of opening ports on the wan for RDP directly.

sorry its taken a long time to respond went on holiday. i added udp tcp ports rule that allow the server.exe file to pass through the windows firewall.

^ yeah, and not only wrong..  But nothing screams performance like hirpinning and letting your edge router/firewall handle traffic that it should never see.  What  sweet setup it must be because setting up dns might take a few minutes ;)