Well for starters on your dhcp server - Here is the thing if your on AD, then your AD really should provide both dhcp and dns.. Just the best solution. As to your configuration of multiwan - yeah prob something wrong with it.. Draw up your network and post your configurations and we can take a  look see.  But without some more details there isn't much anyone can do.

i create the same rule on lan_1 and its now working perfectly.thanks sogutlulu_54 for helping me out.

Nobody?  :(

@adolfo_rodrigues: @phil.davis: You need to enable nat reflection to do that.  Or better method is to have your local hosts directly resolve www.xxx.com to your private IP 192.168.1.2 This is the answer - do one of these. An easy way is to add a host override in DNS Forwarder to define xxx.com to be 192.168.1.2 It is like phill said, I had the same issue here, the workqround was enabling DNS Forwarder to resolve the host and domain to my internal IP from my internal machines. On your case see attached. Hope it helps. Regards. It is working, thank you very much! I have many vhost like test.xxx.com bla.test.com etc… Can I set up so every vhost work also? I have tested it works to add manually each vhost, but is their a way I can take all at the same time?

thank you i know its easy if you got pfsense but i havnt got pfsense yet installed and before i go ahead and buy a pc and install pfsense on it, i want to do my homework before

@clauded1: I'm trying to setup pfsense 2.1 with tinydns to serve DNS for my local net and use forwarder for external addreses. However, I'm not able to get the setup working. DNS forwarder works fine (except pfsense can't find it's firmware updates) but resolution to local.net don't work. Here's my setup : pfsense config: LAN : 192.168.1.1 WAN : DHCP DNS Servers : 8.8.8.8 and 4.4.4.4 I have the same setup and it took me a while to get it going the way I liked: You need to: Services -> DNS Forwarder - DO NOT USE (TinyDNS provides a resolver) Firewall Rules for DNS - Disable - you dont need them NAT Rules for DNS - Disable - you dont need them Services -> DNS Server -> Settings: Binding IP Address: 127.0.0.1 Enable recursive DNS responder - ENABLE Interface to listen - Select them (I use all) Respond to IP - I use "10", because my Internal network uses 10.x.x.x - adjust accordingly System -> General Setup -> DNS Servers Your LAN IP address (you dont need the external ones like 8.8.8.8, etc) Now, I can resolve my own domain names, external addresses and more importantly, pfsense now displays "You are on the latest version." again :)

You need to stop and restart, not reload, dnsmasq to clear its cache.

And why would Lan have a gateway?  Do you have other lan networks that you need to get to? The install does not even ask you for this - so why did you put it on?  What did you put in?  Pfsense own address?

It all worked! Just wanted to thank you. I faced only one issue when DHCP did not update "reverse lookup zone" but it got fixed after specifying proper credentials for update account.

@mendilli: does your access point act as a dhcp sever? if so it may deliver ip and you can not see it in pfsense. you must disable dhcp sever in access point. Thanks for your reply; appreciated  ;D No, it doesn't, I checked. More over, even if it would, it would be strange that it, by accident, would give it the next in line number (x.x.2.14) which happens to be the 'old' fixed ip-nummer that it had before (?) if you give static ip to a network device there is nothing wrong when you can not see it in dhcp leases, dhcp sever shows only the ip's that it is delivering This I didn't understand. If I tell Pfsense to give out a static IP I would see it in the DHCP/status, no?

because something got stuck and system thought it was running because of the pid file, when it really wasnt.  Did you have a power outage or something? So you cleared up the old pid, now if you look there is a new pid file - if you view the contents of the file with cat it will show you a number – the pid..  As you stop and start the service this number will change. If something wrong with the file, or it has a pid number of a running process that is not dhcpd - system can think dhcpd is already running, etc. deleting it just allowed whatever the snafu was to get cleared up.

@jcyr: In the current pfSense bind implementation the static dhcp mappings are only added the zone at the time the zone is saved. Exactly! I wonder if any dev is actually reading this forum …  :-\