I'm not aware of any provider that requires more frequent than that, which are you seeing where that's the case? Generally it's a month or more. That's hard coded in the source, /etc/inc/dyndns.class

Feel so stupid????????? Client isolation was on. I really thought i've shut it of. Thx for the help. Finally my hotspot is running as it should be.

I'm having the same problem! When I Disable "DNS Rebinding Checks", stop squid authentication on AD. I'm studing any solution.  ;D

rajbps, Use one of these reverser proxy servers: squid3 varnish apache2+modsecurity haproxy att, Marcello Coutinho

who may help add the DNSCurve in pfsense? see informations: http://curvedns.on2it.net http://dnscurve.org/crypto.html

In a normal setup, how would the 2k8 server dhcp be able give wan interface of your router address via dchp.  They clearly should not on the same wire (switch) I agree an actual drawing would be nice.  From your post modem –- wan (pfsense) lan -- 2k8 -- clients? Do you have multiple interfaces on 2k8?  Do you man that lan of pfsense connected to switch, and then both clients and 2k8 all connected to same switch? Seems like you must have your pfsense interfaces not connected correctly if 2k8 dhcp is handing it an IP.

Aaaaaand last one (domain controller VM network configuration). [image: DC-netconfig.PNG] [image: DC-netconfig.PNG_thumb]

Went back and deleted all the VLANs again and set them up, one by one, and disabled the DHCP daemon for each one as I went. I was able to get them all setup this way and still have the LAN DHCP service functioning. Went back in and enabled JUST the VLAN40 DHCP server and restarted the DHCP daemon.  It continued to work….. ??? Really didn't do anything different this time, from a setup perspective.  What I did originally should have been fine. Not sure why it's acting normally now.  Hate when things fix themselves!  I'd rather it stay broken so I could understand what the problem was until I fixed it.

So in bridge mode it works fine then?  Connected to pfsense? I run a AP off my pfsense, on my normal pfsense lan and don't have any issues at all. Bridge is a bridge, should not matter what lan its connected too.  Unless you having connectivity issues to your switch behind pfsense in bridge mode it should work just fine. As to in Router mode with dhcp server on the AP – again that has nothing to do with what the AP is connected to or even if connected to anything.  If its not handing out dhcp to wireless or wired clients on its lan interface that would be the AP issue. Now if  your going to use it as router on pfsense -- pfsense would have to have routes to that network on the AP lan side.  Unless the thing is doing nat?  But again you still have to get IPs on the clients before you worry about why you can not get to the internet, etc.

For anyone else having trouble with this particular cycling nic issue, this problem has been previously documented. It was marked as resolved 2 months ago by Chris Buechler. Just as this thread indicates; http://redmine.pfsense.org/issues/1572 The only solution in my particular case was setting the "Speed and Duplex to nothing other than "default"." All cycling vanished. v2.0.1

OpenVPN clients don't register their hostnames in DNS.

Solved the problem by removing the double section "# dhpleases automatically entered" from /etc/hosts manually. I can add new static leases again, and the hosts file is not truncated anymore.

In that case, maybe they won't be a problem, so I'll look into it again. Was just hoping I could setup pfSense equivalently to OpenBSD since that's known to work and would require less configuration on other machines.

Thank you! double checked the dhcp settings and rules, made the change, everything seems to be going fine!