The hostname isn't properly configured in your Kloxo server. The screenshot you posted tells the probable causes. Lots of references out there that undoubtedly have some solutions. http://lmgtfy.com/?q=%22domain+is+pointing+to+the+wrong+kloxo+server%22

The default gateway of public asterix server is going to be the ISP gateway. So you will need to add a static route on public asterix server to tell it that 192.168.1.0/24 is reached through pfSense WAN IP 20.20.1.200 Then have pass rule/s on pfSense WAN to allow traffic source 20.20.1.201 destination 192.168.1.n (the server/s you want to allow it to access) port as needed.

Your firewall rule is only allowing TCP. That will mean that DNS requests from clients (UDP) are being blocked. Clients will not be able to resolve DNS. You can probably ping 8.8.8.8, but not ping by name.

I use the WOL tool integrated in pfSense. Services > Wake On LAN If applicable you can apply a special user for that and give solely the appropriate permission to him in user manager.

Yep. And for reasons like that, it's easier to keep the 127.0.0.0/8 NAT rule in place by default.

Sorry , so slow to reply , I was busy in database setting. Thanks a lot, I found the problem is I should add a DNS mapping too in NAT Outbound just like your reply "on: April 11, 2014, 10:20:53 am »". The  http://mxtoolbox.com/  is very useful, Now I check a domain with DNS&MX  A record is functional, appreciate your help.

@doktornotor: Way damn too long. Post screenshots instead. lulz A single screenshot of the port forward would indeed be worth more than a wall of text in this case.

First thing, disable or remove any packaged or traffic shaping. They are not necessary for the function of the firewall. You will want to get it working before putting on advanced tools. You would only need OPT if you are going to run a DMZ. Otherwise, assign IP Alaises to the LocalHost interface for the extra IPs. Then there will be NAT to work on.

Changed it back to automatic mode and assigned different gateways in the allow all rules for both LAN 1 and LAN 2. That fixed it. Thanks for the support.

Good. ;)

OK. Thanks i will check the approach. Thank you.

Have you set the GW for the LAN - remove it. Have you set a gateway for the WAN - you must have this. Then you need to apply your rules to allow web traffic from LAN to WAN.

I think your in your first screenshot, the second port forward rule is wrong - the destination address should be "WAN address", not your external ip. Change your highlighted virtual IP. [image: FWrule80.png] [image: FWrule80.png_thumb]

@mmhan: Great point! It still would have be ideal to have them serve the site without using non-standard ports though. Well, you could always point the two DNS names to the same IP address and hope that the browser sends the URL as part of the HTTP requests (all modern browsers do this, I believe). Then the web server can figure out what web site to serve up. I know IIS can do this. I assume others can do this as well.