Correct
Using OpenDNS is a easy way to avoid site's with spyware and phishing.

@GruensFroeschli:
You don't have to clutter the web-gui.  Simply look for a standard dhcpclient.conf first and if it exists, use that instead of the values in the code.

@rnilsson:
In my case, the pfsense box was not reconnecting again no matter how long I waited.  Besides, I rely heavily on my voip phone so even the 10 minute wait can be too long.  Most of my outages last only a couple of minutes or less.

Let's assume the first and … cheers!  ;-)))  SCNR

Some additional information is worth noting.

We have a dual WAN setup:

WAN1 - 192.168.254.1
  WAN2 - 192.168.253.1

Systems in the DMZ use WAN2, systems on the LAN use WAN1, so it is somewhat strange that the firewall log is filling with blocked DNS responses going to the WAN1 interface when the systems that should be actively using DNS in the middle of the night are on the DMZ (i.e. email). Occasionally there is a block on the WAN2 interface, so this is not exactly conclusive of anything, but I still find it worth a mention.

Also, the configuration on pfSense is that DNS should be overridden by DHCP on WAN, and DHCP on WAN provides pfSense with the ISP DNS server addresses. I have tried statically setting the DNS servers in pfSense with the same result.  :-\

Oops. Decided to experiment with clean box. Installed OF1.2 with simpliest setup LAN-WAN (only two interfaces, no vlans at all).
Connect laptop with dhcp-client to LAN interface and booooms: on WAN interface I see DHCP broadcast with 255.255.255.255 as destination IP.
I can provide any details. Please explain why it happens…

Thanks.

Does anybody have any idea about this?  Even on a fresh install pfsense seems to stop showing information from the DHCP logs after a short period.

Ah, thank you very much. I'll have to try this when I get back to the office. I'd do it from home, but I can't get to it from the outside world yet. Guess I forgot to enable that! D'oh!
But thank you for your quick response. I can't believe I missed something so simple. Surf Wisely!

Problem turned out to be a broke ass Juniper (Unishpere) Erx that had to have the current DHCP lease cleared.  It would ignore new requests or releases.

Well, your suggestion doesn't work. Adding the invalid .255 IPs to the static leases, I'm getting the following error message in the web interface:

    * 192.168.24.255 is inside the range you specified.     * 192.168.25.0 is inside the range you specified.     * 192.168.25.255 is inside the range you specified.     * 192.168.26.0 is inside the range you specified.     * 192.168.26.255 is inside the range you specified.     * 192.168.27.0 is inside the range you specified.     * 192.168.27.255 is inside the range you specified.     * 192.168.28.0 is inside the range you specified.     * 192.168.28.255 is inside the range you specified.     * 192.168.29.0 is inside the range you specified.     * 192.168.29.255 is inside the range you specified.     * 192.168.30.0 is inside the range you specified.     * 192.168.30.255 is inside the range you specified.     * 192.168.31.0 is inside the range you specified.

Any other suggestions? My DHCP range is 192.168.24.0-192.168.31.255.

There are only 2 places:

Under the general settings where you set the DNS-server for pfSense itself.
This is the server the DNS-forwarder will use to resolve external addresses.

And on the DHCP-server config-page.
This is the DNS-server the clients will recieve.

@GruensFroeschli:

You bridged multiple Interfaces to the same "virtual hub".
Traffic comes in on one interface and goes out another into the same network.

yes GruensFroeschli you are right, i have the same problem and i fix now

Traffic comes in on one interface and goes out another into the same network.

thanks GruensFroeschli

Update to dnsmasq (2.46) on pfsense 1.2:

killall dnsmasq
mv /usr/local/sbin/dnsmasq /root/
fetch -o /usr/local/sbin http://rz-home.de/~hhornung/dnsmasq
chmod +x /usr/local/sbin/dnsmasq
/usr/local/sbin/dnsmasq