For me it's sound like you somehow have messed up your configuration or are having a hardware problem.
upgrade to 1.2.3 http://blog.pfsense.org/?p=377
http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/

But in the end I would bet that reinstall will be a better approach.

Might help http://pfsense.site88.net/multiwan.html

@cmb:

Yeah it should only run on the master. It does work running on both, though it really shouldn't.  bug ticket open on it.
http://cvstrac.pfsense.org/tktview?tn=1883

Thanks ! :)

Yeah that looks good.

Next I'd get a capture from the DHCP server to ensure the relayed requests are getting there, and if they are then enable audit logging on the Windows server and see what it's showing.

Two things…

#1: Another way to make a change like this is without a reload is:

Make a backup (just to be safe!) Load up a WebGUI page with a save button Switch to a console window Edit /cf/conf/config.xml rm /tmp/config.cache Click "Save" on the WebGUI page you loaded earlier.

#2: Having said that, I was able to get a third DNS server to take this way -- but -- as soon as I went back to "System > General Setup" and clicked "Save" there, it wiped out the additional DNS servers.

So it might work, but YMMV...

You don't have to change anything, DNS will resolve from any interface IP and CARP VIP. Your firewall rules have to allow that query traffic.

Heres some links to pfsense features

http://www.pfsense.org/index.php?option=com_content&task=view&id=40&Itemid=43

and captive portal

http://doc.pfsense.org/index.php/Special:Search?search=captive+portal&go=Go

I personally use it as many others do as well and it works great, on both wired and wireless networks, I think you'll find it easier to manage users than what youre currently doing, no point trying to reinvent the wheel.

You can find it under Services/Captive portal on the pfsense gui.

Slam

I found the answer…..

The problem was not PFSense at all, but an OpenDNS setting and the way Windows handles lookups.

Windows lookups go in this order:

HOSTS file
DNS Server
NetBIOS Name Table

For NetBIOS names to lookup correctly, the first 2 options have to fail.  With the "typo correction" feature enabled on OpenDNS, #2 never fails and thus Windows never gets to look for a NetBIOS name.

Registering a OpenDNS account and turning off typo correction fixes the problem.  Of course a proper AD/Domain setup would as well...

System -> General Setup

I would rather set the openDNS servers onto the "allowed IPs" list than allow the client alltogether.

It is listed. When I set up my static DHCP lease I made sure to put in a hostname.

I'll look thru that post and see if I get any further.

It's driving me nuts!

if u have apache just install plesk and all it`s done. U can do this easy from Plesk panel.

I think he means the DNS entries and the Static IP entries are found in two different sections.

Input your IP# and Gateway in the WAN config section under Interfaces and the DNS entries can be found in the General settings page.

Thanks.

With a few more options, like separate list of the internal DHCP leases registered in DNS, and per domain and/or time sorting would be very interesting.
Will try to offer something in the near future, as soon as I finish other pressing issues around my network and pfSense.

;-)

Your pfSense doesn't know about your actual WAN IP, thus it cannot promote it to DynDNS service.
However, it correctly promotes what is known: it's WAN IP. That's not the LAN IP you pointed to earlier!

Two possibilities:

let your modem do the DynDNS update itself (it knows the WAN IP) (if at all possible) switch your modem to bridge mode and have pfSense do the PPPoE. This way it knows the WAN IP and can update your DynDNS settings correctly.